When you enable trace flag 1200 SQL Server gives you extensive information about all the locks being taken by a specific query or procedure.
There is a little behavior change between SQL Server 2000 and SQL Server 2005 however. In SQL Server 2000 it was a session wide flag so DBCC TRACEON (1200) was enough to get you going while SQL Server 2005 considers it a server wide flag meaning you have to use DBCC TRACEON (1200, -1) to get it going again.
Thanks to Dirk G from MCS Belgium for clearing out the difference in behavior between SQL Server 2000 and SQL Server 2005.
For SQL Server 2000 you do the following:
DBCC TRACEON (3604)
DBCC TRACEON (1200)
For SQL Server 2005 you do the following:
DBCC TRACEON (3604)
DBCC TRACEON (1200, -1)
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment