Do not log job history

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2008 » SQL Server 2008 Administration » Do not log job history

Do not log job history

Rate Topic

Display Mode

Topic Options

Author

Message

George Luiz

Posted Tuesday, March 19, 2013 7:03 AM

Forum Newbie

Group: General Forum Members
Last Login: Wednesday, June 05, 2013 8:16 AM
Points: 7, Visits: 36

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

opc.three

Posted Tuesday, March 19, 2013 9:46 AM

SSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 1:24 PM
Points: 6,826, Visits: 11,950

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

Believe you can and you're halfway there. --Theodore Roosevelt

Everything Should Be Made as Simple as Possible, But Not Simpler --Albert Einstein

The significant problems we face cannot be solved at the same level of thinking we were at when we created them. --Albert Einstein

1 apple is not exactly 1/8 of 8 apples. Because there are no absolutely identical apples. --Giordy

Post #1432749

George Luiz

Posted Tuesday, March 19, 2013 10:39 AM

Forum Newbie

Group: General Forum Members
Last Login: Wednesday, June 05, 2013 8:16 AM
Points: 7, Visits: 36

Thanks!

Post #1432771

CapnHector

Posted Wednesday, March 20, 2013 2:03 PM

SSC Eights!

Group: General Forum Members
Last Login: Thursday, June 06, 2013 3:00 PM
Points: 939, Visits: 1,713

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 »

Permissions