Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a peculiar situation. I have tables that are constantly accessed by different parts of our code and thousands of clients and so we employed the use of transactions when doing simple updates and inserts on our tables. Problem is we keep getting deadlock errors. Anyone have any idea how I can alleviate this problem?
Deadlocks can arise for many reasons and combinations thereof:
Poor schema design
Incorrect indexes for your query
workload
Poorly written TSQL
Aggressive transaction isolation levels and/or long running open transactions
Poor application access patterns
Low spec or incorrectly configured
hardware
All of these are common.
I suggest you read
Using SQL Server Profiler
Analyzing Deadlocks with SQL Server Profiler