May 31, 2007 at 1:37 pm
Our web server has worked fine in a multi-user environment with multiple users updating small numbers of records against a SQL Server 2000 DB. We have recently had users significantly increase the number of records they are updating and now seeing a dead lock error (1205). My thought is that it was doing row locking, but is now choosing to do page or table locking.
We have demonstrated that we still get the dead lock between 2 users even when they are updating different records based on record ids. I am struggling with SQL Profiler to track this down.
Does anyone have suggestions on how to make DBCC TRACEON work?
I ran DBCC TRACEON (3605,1204,-1) in SQL Query Analyzer, but don't see anything in the log file when I recreate the deadlock in our web server application.
June 1, 2007 at 6:49 am
I found this article when I trying to resolve a deadlock issue:
http://www.code-magazine.com/Article.aspx?quickid=0309101
MG
"There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies."
Tony Hoare
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
June 1, 2007 at 7:47 am
Thanks for the response.
In conjunction with the article you pointed out, I have used the article below to successfully setup additional logging for the deadlock issue.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply