March 28, 2003 at 9:15 am
Whenever your server is started run:
DBCC TRACEON(1204,3605,-1)
This will put all the details that caused the deadlock into your SQL Server Logs, including the SP's and line numbers that caused it.
PlanetJam Media Group
PlanetJam Media Group
March 31, 2003 at 5:22 am
Thanks for that.
I note that flag 1205 shows more detailed info - is this a good idea instead of 1204, or does it generate too much info? Is 1204 sufficient to tell me which SQL is causing the deadlock?
Trace 3605 says it logs to the error.log - is this the Win server log, or a SQL Server log?
quote:
Whenever your server is started run:DBCC TRACEON(1204,3605,-1)
This will put all the details that caused the deadlock into your SQL Server Logs, including the SP's and line numbers that caused it.
PlanetJam Media Group
Viewing 2 posts - 16 through 16 (of 16 total)
You must be logged in to reply to this topic. Login to reply