August 27, 2011 at 11:23 pm
Hi,
We have SQL Server 2005 EE with SP3. Today, I noticed a starnge thing on our production failover cluster instance. The sqlserveragent is NOT showing up the history of jobs.
For example, the full backup job runs every day and I'm able to see the messages in error log that the databases are backing up successfully but job history is showing nothing!!
What could be the issue? Because I need to check how much time the job is taking to finish.
I remember, I have verified the job history 2 weeks ago and I was able to see all job history..Some thing is happen after that and sqlagent is NOT showing up any job history.
Please advice
August 28, 2011 at 10:42 am
First, run an integrity check on the MSDB database:
CHECKDB(msdb) WITH no_infomsgs, all_errormsgs;
If that comes back clean, then look for a maintenance task that is set to cleanup history. Validate the settings are not removing history right away.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
August 28, 2011 at 10:05 pm
I ran the below command and it's ran successfully
DBCC CHECKDB(msdb) WITH no_infomsgs, all_errormsgs;
There is NO maintenance plan to remove history.
Please advice what else I need to check?
August 28, 2011 at 10:12 pm
If there isn't any database corruption - then my guess is someone cleared the history. How are you checking the job history?
Wait...just realized you are talking about jobs. What are your settings for the agent history? If this is the default, then you could be running into an issue where another job is taking up all of the allocated space for your history.
I uncheck the default option - and build a maintenance plan to clear history using the History Cleanup task. I set the values here for 6 months - which does this per job instead of how the agent deletes history for all jobs.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
August 30, 2011 at 10:16 am
Wait...just realized you are talking about jobs. What are your settings for the agent history? If this is the default, then you could be running into an issue where another job is taking up all of the allocated space for your history.
I uncheck the default option - and build a maintenance plan to clear history using the History Cleanup task. I set the values here for 6 months - which does this per job instead of how the agent deletes history for all jobs
Yes Jeffrey, I'm talking about job history.
The default option is selected. I can Uncheck and set up a maintenance plan to clear history using the History Cleanup task.
Before that I want to make sure that other jobs are taking up all of the allocated space for the history. How to find that?
Please advice
Thanks
August 31, 2011 at 2:33 am
Hello,
Have you checked SQL Server Agent Properties, Under that you will find History tab and from there you can come to know that ' The current job history log size', limit size of job history log'.
Here it seems you might have set something wrong here..
Please check setting and get back to us accordingly.
Thanks.
SurendraP.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply