Solved

Sql Server Agent Job Logs

Posted on 2014-09-03
3
329 Views
Last Modified: 2014-09-03
Hi All,

I have a bunch of jobs on a server.  Some of the jobs are not reporting any history.  I'm pretty sure this is due to the fact that there's a heart beat job running on the server (runs once a minute, every minute, every day).  

Is there a way to configure SQL to either (in order of preference)

1)  Not log the heartbeat job
2)  Limit the size of the jobs to X number of instances (eg: keep only a record of the last number of times run).
3)  Expand the log size to accommodate everything

Thanks in advanced.
0
Comment
Question by:Kyle Abrahams
3 Comments
 
LVL 47

Accepted Solution

by:
Vitor Montalvão earned 350 total points
ID: 40301393
3)  Expand the log size to accommodate everything

In SSMS go to SQL Server Agent and right-click for properties and make the changes you need in History.
Capture.PNG
0
 
LVL 69

Assisted Solution

by:Scott Pletcher
Scott Pletcher earned 150 total points
ID: 40301428
I prefer to uncheck the "Limit size" and specify a "Remove agent history" time period.  You can specify 3 months if you want.  That keeps all history for a full three months, rather than a raw row count, which could of course be inflated by frequently run jobs.
0
 
LVL 40

Author Closing Comment

by:Kyle Abrahams
ID: 40301520
Thanks guys.
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
insert wont work in SQL 14 21
Update a text value in another table 10 40
Increment column based of a FK 8 22
access query to sql server 3 20
In this article we will get to know that how can we recover deleted data if it happens accidently. We really can recover deleted rows if we know the time when data is deleted by using the transaction log.
JSON is being used more and more, besides XML, and you surely wanted to parse the data out into SQL instead of doing it in some Javascript. The below function in SQL Server can do the job for you, returning a quick table with the parsed data.
This video shows, step by step, how to configure Oracle Heterogeneous Services via the Generic Gateway Agent in order to make a connection from an Oracle session and access a remote SQL Server database table.
Via a live example, show how to shrink a transaction log file down to a reasonable size.

773 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question