Query Governor - possible to exclude replication jobs? 
Author Message
 Query Governor - possible to exclude replication jobs?

I know that I can turn off the query governor for individual connections, but
am not sure how to go about doing that with replication jobs.  I'd like to set
my query governor to 300 (or less ideally) for our prod system, but the
estimated time for the replication jobs is 648 (or close to that).  As soon as
I applied the query governor, I got all sorts of alerts telling me that
replication couldn't run.

Any ideas on how to exclude replication?  Do I have to modify the system procs
in order to do this?  Is it even possible?

Thanks in advance.

-Pete Schott



Mon, 31 Oct 2005 15:18:03 GMT
 Query Governor - possible to exclude replication jobs?

I don't think you will be able to exclude rep from the query governor.  The
only option I can think of is that you provide (or edit) the Stored
procedures generated which do the replication to each use the SET command to
increase or turn off the limit.

--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), C{*filter*}te, NC
www.computeredservices.com
(Please respond only to the newsgroups.)

I support the Professional Association of SQL Server (PASS) and it community
of SQL Server professionals.
www.sqlpass.org



Quote:
> I know that I can turn off the query governor for individual connections,
but
> am not sure how to go about doing that with replication jobs.  I'd like to
set
> my query governor to 300 (or less ideally) for our prod system, but the
> estimated time for the replication jobs is 648 (or close to that).  As
soon as
> I applied the query governor, I got all sorts of alerts telling me that
> replication couldn't run.

> Any ideas on how to exclude replication?  Do I have to modify the system
procs
> in order to do this?  Is it even possible?

> Thanks in advance.

> -Pete Schott



Mon, 31 Oct 2005 21:26:44 GMT
 Query Governor - possible to exclude replication jobs?
I probably should have been more specific.  Don't know what I was thinking:

SQL 2000 - SP2 servers all around.
Windows 2000 SP3 underneath

Task that failed is the distribution agent.  Looking at those jobs, they run a
Replication Distributor job in there.  What would I modify to put the SET
statement in the job so the connection wouldn't be affected?  Do I really have
to hit all sorts of stored procedures to do this or can I just do one or a
handful?  Does this even use stored procedures?

I appreciate the help.  I can't effectively use the Query Governor option
unless I can exclude replication and it's giving me some LONG estimated run
times for this job for how long it actually runs.

Thanks.

-Pete Schott

Quote:

> I don't think you will be able to exclude rep from the query governor.  The
> only option I can think of is that you provide (or edit) the Stored
> procedures generated which do the replication to each use the SET command to
> increase or turn off the limit.



Mon, 31 Oct 2005 19:17:12 GMT
 
 [ 3 post ] 

 Relevant Pages 

1. Bit-Map Indexes and Query Governors

2. Estimated Exec Time & Query Governor

3. Query Governor Cost Limit Values

4. query governor

5. question about "query governor cost limit "

6. Query Governor

7. query governor cost

8. 2000 Query Governor

9. Query Governor - Good or Evil?

10. Query Governor?

11. Query Limiter/Governor

12. Query Governor for System 11


 
Powered by phpBB® Forum Software