Profiler replay with more than one DB

microsoft.public.sqlserver.tools

11 May 2007 5:59 PM

FredDBA

Hi,
in order to reproduce the production workload I am trying to use the replay
trace functionality of the profiler v.2005. I did everything the doc says,
same dbid, same logins/users/passes, use the traceSQL template, etc..

On my prod server I trace calls for our webServer login. The web
application calls procedures into 3 distinct databases. So I trace them all
3.

Then I replay the trace log into my test server whereas the DBIDs are the
same as in the Prod server. Just before replaying the trace I can see in the
trace log that some calls are within dbid X others dbid y while the rest on
dbid z.

My problem is when I replay the log it seems to call them in ONLY one
database, so every calls that are supposed to be done on the 2 other DBs are
obviously failing. I did not see any options regarding this, I tried to
boost the number of connections the profiler can use to make sure it doesn't
re-use the same pipes...

Any ideas on this would be much appreciated.

Ohh and one more ;-)

It seems every time the profiler opens a pipe the first thing I get on the
reply monitor is "Failed to set proper user name ('webServer') for the
connection"
Regardless, it seems to manage itself to connect and runs the procedures
just fine, my guess is that I should see this as a sort of warning... but
still it worries me a bit.

Regards

FredDBA