SQL Server Performance Forum – Threads Archive
query governorWe have a MS Access aplication that uses MS SQL 2005 as back end. We have a client that locks up when a particluar query is run. It does not happen all the time but when it does it appears that this query is the culprit. We are rewriting the query for the long term fix. For the short term i wanted to know if using the query governer to kill the query if runs too long (over 10000 ms) will do the trick? or am i just barking up the wrong tree?
you will need to check the plan cost for this MS access query
if it is 100, then you could set the query governor to 90, which should prevent a plan cost of >90 from running,
but what other queries will this stop? why don’t you just not run this for now, instead of taking action that might cause other problems