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.
| Author |
Topic |
|
Getzin
Starting Member
6 Posts |
 Posted - 2009-09-10 : 02:53:54
|
| I have a production database where there has been no change in T-SQL in the last 3 months. Also daily transactions (type as well as count) has not changed during this period. Suddenly too many deadlocks have started appearing. Added lock hints to select and update statements, and the deadlocks vanished.Is it possible that select and update statements have a default behaviour, if lock hints are not provided and these behaviour has changed due to installion of some service pack?I have no way of finding out whether the user has installed any SP as the user does not record such activities.Shekar |
|
|
webfred
Master Smack Fu Yak Hacker
8781 Posts |
Posted - 2009-09-10 : 03:01:34
|
Maybe there are 'suddenly' more concurrent sessions than before?
No, you're never too old to Yak'n'Roll if you're too young to die. |
 |
|
|
Getzin
Starting Member
6 Posts |
Posted - 2009-09-10 : 03:12:21
|
| There is no change in concurrent connections. |
|
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2009-09-10 : 18:39:03
|
| You need to look on1) Better Indexing Strategy2) Check with performance counters for Memory,Disk,Processor Bottlenecks3) Tweak in the code |
|
|
|
|
|
|
Sudden deadlock appearence