July 2, 2008 at 1:05 am
We want to limiting resource intensive queries on our SQL2005 transactional system - particularly at month end.
As documented the only method to do this in 2005 appears to be the query governor cost limit config parameter or the set QUERY_GOVERNOR_COST_LIMIT connection setting.
Has anyone experience with this? Or are there any alternatives.
I will be looking at this over the next month or so and will post my experiences here.
regards
John Reidy.
March 8, 2010 at 7:03 am
I need to do this based on the login/user. Did you get any responses that helped?
Kindest Regards,
David
** Obstacles are those frightening things that appear when we take our eyes off the goal. **
March 8, 2010 at 10:26 pm
If you know the database, user or application or even table for your critical stuff you can query various DMVs to see executing queries and the amount of effort (CPU, IO, etc) that they are using. If they get unwieldy then kill them. just set up a polling job to watch for the hard hitters that aren't critical. If you have pure sproc access you could also disable access to the bad boys using security changes. Or you could swap in code that has waitfor delay code sprinkled troughout it. Lots of options here. 🙂
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply