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 |
|
amitmnagarwal
Starting Member
15 Posts |
 Posted - 2009-02-12 : 10:06:38
|
| We did migration of MSPROJECT 2003 - MSPROJECT 2007.Since then we have been facing lot of performance issue with the new product as MS have converted from int to GUID.This might be one reasonWe are consitently facing Timeout errors and Transaction (Process ID 55) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transactionWould like to know what could be the reason.Also some tips to improve the performance SQL Set Up1) Two BOX BOX1 - This is in cluster with BOX22) BOX3BOX1 and BOX2 are in clusterand talk to BOX3 via linkserver. |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2009-02-12 : 10:21:05
|
| Do you know what you are running? We need details of Trace flags or SQL profiler Deadlock graph to analyze what is going on? You can 'SET DEADLOCK PRIORITY LOW' in transaction if you want to set some process to be victim and Rollback? |
 |
|
|
|
|
|
Performance Issue -GUID