Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL 2012 locking blocking and deadlocks Expand / Collapse
Author
Message
Posted Thursday, April 10, 2014 9:33 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, August 15, 2014 3:42 PM
Points: 24, Visits: 111
Question: Is there a time specific setting set for timing out a long running query or a extended lock event?? if so where is it set?
Post #1560506
Posted Thursday, April 10, 2014 9:52 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 8:36 AM
Points: 40,615, Visits: 37,080
Timeouts are a client-side setting, SQL doesn't give up on queries unless it's told to (kill session or attention call from client app)

There's a lock wait setting somewhere (sp_configure I think), but it's instance-wide.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1560513
Posted Thursday, April 10, 2014 11:26 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, August 15, 2014 3:42 PM
Points: 24, Visits: 111
What about the query governor setting for queries? Should that be set? If so any recommendations?
Post #1560559
Posted Thursday, April 10, 2014 11:48 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 8:36 AM
Points: 40,615, Visits: 37,080
It depends. It's definitely not something I'd set everywhere. It doesn't look at the time queries take, it looks at their cost and that's an estimate. It doesn't stop a running query, it prevents queries from even starting if their cost exceeds the threshold set.


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1560565
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse