- You have a computer that is running an instance of Microsoft SQL Server 2000 or of Microsoft SQL Server 2005.
- You use SQL Profiler to perform a client-side trace of the events in the instance of SQL Server.
- You run SQL Profiler on the computer that is running the instance of SQL Server, or you run SQL Profiler on a different computer.
When this problem occurs, you notice the following symptoms if you query the master.dbo.sysprocesses system table in the instance of SQL Server:
- Several active server process IDs (SPIDs) display the 0x404 (LATCH_EX) value in the waittype column.
- One or more SPIDs display the SQL Profiler value in the program_name column.
- MISC (hex address)
- You use SQL Server 2000 Service Pack 4 (SP4) or SQL Server 2005.
- A SPID is waiting to perform synchronization trace operations in SQL Profiler.
Because SQL Profiler is a process that is separate from the SQL Server process, transferring each event to SQL Profiler takes some time. If you run SQL Profiler on a different computer, this process takes longer. This process takes longer because of network latency and because of the performance of the computer that is running SQL Profiler. Therefore, the instance of SQL Server performs slowly.
You can use the following system stored procedures:
Article ID: 929728 - Last Review: Sep 30, 2008 - Revision: 1