June 30, 2010 at 10:53 am
An application developer complained that they were seeing issues with deadlocks in the DB during the nightly processes when it receives applications from vendor1 and vendor2. For vendor1, they saw the issue start around 11:26 last night and continue until 11:29. Almost 200 applications were not processed. For vendor2, they saw the issue start around 3:01 this morning. Almost 300 applications were affected for this.
I made sure that nothing runs during that time except for the Tlog backups.
How do I just allow only this user to access the db and block all other users from accessing the database? I'd like to block them from 11PM to 12AM and from 3AM to 4AM.
Thank you.
June 30, 2010 at 12:56 pm
I would recommend identifying the cause of the deadlocks and resolving it. There is most likely something inside the application code that is causing the deadlocks.
There is already a ton of info on SSC on deadlocks so I won't repeat it all here. Seach SSC for articles on deadlocks.
Limiting access is not going to fix your deadlock problem if the import process is deadlocking on itself.
June 30, 2010 at 1:58 pm
Fix the problem, don't hide the symptoms.
Switch traceflag 1222 on. That will result in a deadlock graph been written to the error log every time a deadlock occurs. Post the result of that graph here.
DBCC TRACEON(1222,-1)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply