1. After verifying all of your options click on the yellow arrow button to start the replay. You should see the output of the trace in the bottom half of the split screen:


    Figure 5.     Output from replaying trace appears in bottom pane of Profiler window

  2. Any errors encountered during the replay should appear in this section as well. Some common errors you might encounter are:
    [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'marker'.
    When you encounter this error verify the following:
    1. The existence of the user in your development environment
    2. The user's password must match the password of the user used to register the SQL Server in Profiler (i.e. the user's password you see specified when you select "Edit SQL Server Registration..." from the Tools menu, then select your server and click Edit)
    [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'authors'.
    This error is most likely caused by the user's default database not being set correctly. You can use the following sql if you like to change the user's default database: sp_defaultdb '<login>' , '<database>'

  3. You can verify that the trace is running by watching the bottom pane of the trace window for output messages. Or you can execute sp_who2 in Query Analyzer and search for the logins of the users in the trace capture.

  4. Execute your new code that you wanted to test for blocking. In my case this is the new sproc that deletes data from 6 tables in the database. While I'm replaying the SQL Trace I start our new sproc. Then I monitor the server activity. The main thing I'm watching for is blocking. You can do this either through Enterprise Manager or the sp_who2 sproc. If you get tired of manually executing sp_who2 every few minutes you can write a script that automatically polls the server for blocking. I wrote one and you can download it here if you like: