October 4, 2012 at 8:34 am
We have a third party application which is reporting Lock Request Timeout Period Exceeded. I ran Profiler against the database and identified the command "Set Lock_Timeout 0" being issued by the spid directly before the timeout occurred. Can anyone think of a reason to set Lock_Timeout to 0 in a production system? It seems odd to me.
October 4, 2012 at 6:32 pm
This must be a side effect of:
EXEC sp_dbgofast
After all, if the Prod system doesn't have to wait for locks, then it must be running faster right?
Seriously, I have no idea. Just thought I'd throw that out there.
My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.
Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply