February 6, 2013 at 6:00 am
Hi All,
I got following Problem on my SQL Server :
The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users. Ask the database administrator to check the lock and memory configuration for this instance, or to check for long-running transactions.
How can I solve it?
Greetz sql pizza
Greetz
Query Shepherd
February 6, 2013 at 6:51 am
Have you got any of the lock escalation traceflags turned on? Are you using any locking hints?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 6, 2013 at 6:54 am
Have you got any of the lock escalation traceflags turned on?
Nope...
Are you using any locking hints?
Got snapshot isolation mode activated. The developers use NOLOCK AND ROWLOCK.
Greetz
Query Shepherd
February 6, 2013 at 7:09 am
SQL Pizza (2/6/2013)
The developers use NOLOCK AND ROWLOCK.
There's a good chance that's a contributing factor (the rowlock usage)
Why snapshot isolation allowed and still using nolock hints? All the downsides of snapshot isolation, all the downsides of read uncommitted and none of the benefits of either.
Maybe worth having a 'chat' with the devs and get them to stop making a mess.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 7, 2013 at 1:07 am
Thanks! This is what I allready suspected, but I was unsure if I'm right and if this would have a real effect...I'll post the results of the action ;-).
Greetz
Query Shepherd
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply