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

Do not log job history Expand / Collapse
Author
Message
Posted Tuesday, March 19, 2013 7:03 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, May 1, 2014 4:14 AM
Points: 11, Visits: 47
Hi,

My SQL Server instances have some jobs that run very frequently ( some execute at every 30 seconds ) and these jobs are consuming all my job history log size and I am losing the history of my main jobs.

I already did some research and found how to increase this log size, but the best would be if I could say to not log some jobs' output. I did some some research, but I did not find anything about it.

Does anyone know if this is possible?

Thanks!
Post #1432625
Posted Tuesday, March 19, 2013 9:46 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 7:06 PM
Points: 7,125, Visits: 12,720
I actually modify the default Agent history settings so that noisy jobs do not force important job history to be deleted. I have a job on all my instances that calls sp_purge_jobhistory to delete history for all jobs older than n-days (depends on instance) and if there are noisy jobs I might call it again for those specific jobs with a shorter retention period.

__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Post #1432749
Posted Tuesday, March 19, 2013 10:39 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, May 1, 2014 4:14 AM
Points: 11, Visits: 47
Thanks!
Post #1432771
Posted Wednesday, March 20, 2013 2:03 PM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Friday, September 19, 2014 5:16 AM
Points: 887, Visits: 1,774
another option i have seen is that if you have a job that is run once a minute and its not triggered by any thing (DB stats logging in my example) is to set it up like follows

WHILE 1=1
BEGIN
DO STUFF
WAITFOR DELAY '00:01:00'
END

That way the job "Runs" once a minute but you dont get the log clutter.



For faster help in answering any problems Please read How to post data/code on a forum to get the best help - Jeff Moden for the best way to ask your question.

For performance Issues see how we like them posted here: How to Post Performance Problems - Gail Shaw

Need to Split some strings? Jeff Moden's DelimitedSplit8K
Jeff Moden's Cross tab and Pivots Part 1
Jeff Moden's Cross tab and Pivots Part 2

Jeremy Oursler
Post #1433468
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse