Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-10-29 : 09:07:54
|
| Mark writes "I am trying to use Profiler to replay a trace from our production server to simulate a production load on a test server for a new version of one of our in house applications. I have backed up the master database and the target application database from our production server and restored them on the test server.I captured all of the events and data columns specified in Books Online for Replaying Traces, including the connection events (Connect, Disconnect and ExistingConnection), but when I play the trace back, I get Replay Errors "[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'db_user'." No other errors get generated. Playback mode I used was Full Synchronization and Maintain Interval between Events.I captured the trace using the test server and am playing it back from there. As I watch the performance of the server with Performance Monitor, the SQLServer process is doing nothing, SQLTrace is using cpu but no connections are getting made that I can see with Query Analyzer.My expectation was that the SQLServer process would get as much work as it did on the production server during the captured time and that I would see all of the connections that existed on the production server. Are my expectations wrong or is there something wrong with my capture or playback setup?In case it makes a difference, we are using MSSQL Server 7.0 with no service packs running on NT 4 sp6.Thanks,Mark" |
|
|
Kevin Snow
Posting Yak Master
149 Posts |
Posted - 2002-10-31 : 16:43:40
|
quote:
In order to replay a trace against an instance of SQL Server (the target), other than the computer originally traced (the source), either: Database IDs on the target must be the same as those on the source. This can be accomplished by creating from the source a backup of the master database, and any user databases referenced in the trace, and restoring them on the target.
Are there any databases referenced in the trace that were NOT restored to the test machine?quote:
Replay ConsiderationsSQL Profiler cannot replay traces: Captured from connections that connected to an instance of SQL Server using Windows Authentication Mode. For information about Windows Authentication Mode, see Authentication Modes.Containing replication and other transaction log activity.Containing operations that involve globally unique identifiers (GUID). For information about GUIDs, see Autonumbering and Identifier Columns.Containing operations on text, ntext, and image columns involving the bcp utility, BULK INSERT, READTEXT, WRITETEXT, and UPDATETEXT statements, and full-text operations.Containing session binding: sp_getbindtoken and sp_bindsession system stored procedures.
Can we assume none of these apply?Edited by - Kevin Snow on 10/31/2002 16:44:23 |
 |
|
|
|
|
|
|
|
SQL Profiler problem