ok, here is my scenario. Our users are complaining about "general system slowness". Some of my developers have heard about some locks or deadlocks that "buried way down deep in SQL Server and they think it might be a problem"
CPU on the Production server never goes about 5%, Memory is low. No Metric I can see is anything but happy happy happy. I don't see any unusual locks we have seen a few deadlocks but they were days ago.
Doing some more research I see that by default
select @@LOCK_TIMEOUT
SET LOCK_TIMEOUT -1; --Wait Forever
But all of the examples that I see end fairly shortly. If I
SET LOCK_TIMEOUT 500;
Then is deadlocks end quickly. But there does not appear to be a system wide way to SET LOCK_TIMEOUT only per session.
Any thoughts?
Thanks
Simian
CPU on the Production server never goes about 5%, Memory is low. No Metric I can see is anything but happy happy happy. I don't see any unusual locks we have seen a few deadlocks but they were days ago.
Doing some more research I see that by default
select @@LOCK_TIMEOUT
SET LOCK_TIMEOUT -1; --Wait Forever
But all of the examples that I see end fairly shortly. If I
SET LOCK_TIMEOUT 500;
Then is deadlocks end quickly. But there does not appear to be a system wide way to SET LOCK_TIMEOUT only per session.
Any thoughts?
Thanks
Simian