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.

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 deadlock detection

Author  Topic 

AskSQLTeam
Ask SQLTeam Question

0 Posts

Posted - 2002-06-20 : 08:30:45
Adrian C. writes "I am using an SQL Server 2000 Enterprise on Windows 2000 SP2.
What I am trying to do is to detect some deadlocks in the database, more precise in some stored procedures that another programmer wrote.

The stored procedures contain some transaction, all with the default level of isolation (READ COMMITED), so the conversion deadlock is out of the question. The order of the updates and delete operations seems to be the same, unless i am missing something.

I tried to use the Profiler tool to see if i am able to see not only the victim of the deadlock but the other process too, but I failed in do so.

Then I tried to configure the SQL Server to use the 1024 trace flag. With "DBCC traceon(1024)" method i realised exactly nothing. I have tested two sample procedures who produce a sure deadlock but the output window of the Query Analizer is just showing Error 1205 and no additional information.

Then I have started SQL Server from console:
sqlservr -c -T1024
and I was succesfull for a single time. When i have tried to do it again and to redirect the console output into a file(adding -eFIlename.txt option to the previous command) i failed again. The additional information doesn't appear anymore in the console and neither in the file.

Worse, when I have tried the previous command again, no effect. No additional information, just the old 1205 error in the Query Analyzer.

Please tell me where I was wrong, in order that i could see for sure in the console or the output file or error log the information i need to resolve the deadlock."

YellowBug
Aged Yak Warrior

616 Posts

Posted - 2002-06-20 : 08:51:30
Trace flag 3605 should also be set. This trace flag sends trace output to the error log.

Search this site for "trace flag" or deadlocks.
And there is lots more information available online.
Go to Top of Page
   

- Advertisement -