2000 Query Governor 
Author Message
 2000 Query Governor
Hello,

I've got a Win 2000/SQL Server 2000 server with a performance problem.  It's
a shared system and some users tend to hog resources with long queries.
Aside from the obvious steps I can take such as seperating traffic to
different servers I was thinking of trying the "Query Governor" setting in
the SQL Server.  Has anyone ever tried this?  Did it work? It looks like it
could cause more trouble than it's worth but I was wondering if it's a
viable solution.

Thanks for any help,

GC



Sun, 22 May 2005 21:23:02 GMT
 2000 Query Governor

GlennC
Have you checked why these queries does take long time?
Perhaps you need to fix t-sql code ,joins ,indexes and et.


Quote:
> Hello,

> I've got a Win 2000/SQL Server 2000 server with a performance problem.
It's
> a shared system and some users tend to hog resources with long queries.
> Aside from the obvious steps I can take such as seperating traffic to
> different servers I was thinking of trying the "Query Governor" setting in
> the SQL Server.  Has anyone ever tried this?  Did it work? It looks like
it
> could cause more trouble than it's worth but I was wondering if it's a
> viable solution.

> Thanks for any help,

> GC



Sun, 22 May 2005 21:28:45 GMT
 2000 Query Governor

Quote:
> I've got a Win 2000/SQL Server 2000 server with a performance problem.
It's
> a shared system and some users tend to hog resources with long queries.
> Aside from the obvious steps I can take such as seperating traffic to
> different servers I was thinking of trying the "Query Governor" setting in
> the SQL Server.  Has anyone ever tried this?  Did it work? It looks like
it
> could cause more trouble than it's worth but I was wondering if it's a
> viable solution.

You may want to use the Profiler utility to capture the queries that are
long running, and determine what needs to be revised; T-SQL, additional
indexes, etc.

Steve



Sun, 22 May 2005 22:07:13 GMT
 2000 Query Governor
I've run into cases where a few users take up an
inordinate amount of server resources by writing queries
with any regard for indexes, optimization, etc.  The
solution we used to address the problem was to monitor the
database for long running queries by any of these users.  
If a query was taking up too many resources, we simply
killed their spid and revoked their permissions.  We then
offered to develop stored procedures (appropriately
optimized) to extract the data that they needed.  We then
wrote the stored procs and granted permission only to the
procs they needed.  

This seemed to address the problems.  At first there was a
bit of resistance, but in the end everyone (including the
people running long queries in the first place) saw that
their queries and applications performed better and they
had less work to do.  It was also less work for the DBAs
since they didn't have constantly deal with performance
problems.  In the end, everyone was happy.

Chris Cubley
www.queryplan.com

Quote:
>-----Original Message-----
>Hello,

>I've got a Win 2000/SQL Server 2000 server with a

performance problem.  It's
Quote:
>a shared system and some users tend to hog resources with
long queries.
>Aside from the obvious steps I can take such as

seperating traffic to
Quote:
>different servers I was thinking of trying the "Query

Governor" setting in
Quote:
>the SQL Server.  Has anyone ever tried this?  Did it

work? It looks like it
Quote:
>could cause more trouble than it's worth but I was
wondering if it's a
>viable solution.

>Thanks for any help,

>GC

>.



Sun, 22 May 2005 23:46:50 GMT
 
 [ 4 post ] 

 Relevant Pages 

1. Query Governor Cost Limit Values

2. Estimated Exec Time & Query Governor

3. Query Governor?

4. query governor cost

5. Query Governor - Good or Evil?

6. Query Limiter/Governor

7. Bit-Map Indexes and Query Governors

8. Query Governor - possible to exclude replication jobs?

9. Query Governor for System 11

10. question about "query governor cost limit "

11. query governor

12. Query Governor


 
Powered by phpBB® Forum Software