By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,379 Members | 1,380 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,379 IT Pros & Developers. It's quick & easy.

Deadlock issue... (not the average deadlock)

P: 6
Okay, here goes... deadlocks have been occurring since Dec 17, 2007 on database; however, no changes were made to the code or the database. The application had been in production for 1 1/2 years before the deadlocks began occurring. On Dec. 17, 2007 two KB updates from Microsoft were installed but neither was SQL related. One for Daylight Savings and the other for a Macrovision driver exploit. Also, our ISP was changed and a new database that had some issues was put into production around this time. The deadlocks have been traced but they (each deadlock) points to a different table. Everything is in stored procedures. The deadlocks occur on 5-6 tables in a 35 table database. Any ideas? I ruled out the usuall suspects... because the db had been in production for 1 1/2 years before any problems surfaced.
Apr 7 '08 #1
Share this Question
Share on Google+
1 Reply

Expert 2.5K+
P: 2,878
Maybe this could help.

-- CK
Apr 7 '08 #2

Post your reply

Sign in to post your reply or Sign up for a free account.