August 16, 2010 at 8:55 am
Just as a test, I make a trace file using Profiler (SQL Server 2000) with the replay template. While the trace is running I make a small data change. and end the trace. I restore the db in-place to the version that existed just before the trace.
Next, I start another trace. While the trace is running, I replay the first trace. When that completes, I stop the current trace capture.
The result is that the data change captured in the first trace is indeed re-effected as expected, the data is changed again. However, none of these data change actions are recorded in the new trace.
I'm trying to COMPARE the two traces to compare performance so I need to be able to make a trace of the replay. Why doesn't this work?
Thanks.
August 16, 2010 at 9:22 am
Well the first thing that comes to mind is, what version of SQL Profiler are you using? You mention a 2K database are you using 2K profiler or 2K8 profiler?
What profile are you using? If you are not using SQL for Replay you may want to pick that one and try again.
August 16, 2010 at 9:32 am
We're using 2K server and 2K Profiler. Also using the replay template for the trace like you're supposed to. The trace appears to replay OK--it changes the data in the expected way--it just seems that the replayed actions are invisible to the OTHER instance of Profiler (have also tried running it on a separate machine, saving the data to another machine, etc., still no dice.)
August 16, 2010 at 9:36 am
So when you say invisible, are you saying that when you go to read the trace file it does not appear or if you are running two traces at the same time?
Also do you have any filters set?
August 16, 2010 at 9:43 am
The only thing I can think of is that by default, profiler excludes its own application name.
So you may get different results by removing that filter from the 2nd trace window that captures the replays...
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply