October 11, 2006 at 4:16 am
Hi,
I have a strange problem. In Entreprise Manager/ management/ SQL Server Agent/Jobs... I can not see anymore the history for any job, no matter is enabled or not. Please, any sugestions , any help ????
October 11, 2006 at 8:10 am
Hi,
Do you have quite a few jobs that are running every few minutes (like replication agents). These may be filling up your history log.
You could try increasing the number of rows stored in the history log.
HTH
Regards..Graeme
October 11, 2006 at 8:23 am
Hi, Graeme
Thanks for your answer.
I have around 40 jobs. The value of parameters are default, 1000 rows per total and 100 rows per job and have worked fine till a week ago. What is realy interesting is that in msdb database I have NOTHING in sysjobhistory and I don't know why ????. It's seems that something stops, blocks recording what happens in SQL Agent
It's really disturbing, because this server hosting the datawarehouse database and all the jobs wich complete the consolidation mechanism.
October 11, 2006 at 9:00 am
Sounds like you have a problem with your MSDB database. Have a go and see if any of the followuing helps?
- Is the 'current job history log size' also displaying 0 rows?
- Anything in the SQL or system EventLog that shows an error with the job? Make sure the jobs are set to log properly under the notifications tab on failure or try changing it to on success and see if you get any useful information.
- Create a basic job (that just does a select or something) and run it during a quiet time whilst watching the sysjobhistory table to see if any rows are added?
- How large is your MSDB database?
- How often do you backup your system databases and when was the last time you backed up MSDB? Do you store a limited amount of historical backups on the server, if so can you see a distinct change in backup sizes for the MSDB database recently which would signify a problem?
ll
October 13, 2006 at 12:54 am
Hi,
and thanks for your support.
Here are the answers:
1. The current job history log size is 0 and remains 0.
2. No speciall errors in SQL Log or EventLog
3. MSDB has around 30 MB and the backup is scheduled every night.
Something strange I did observe, I put the recovey model back to full and this morning is again to simple recovery model. I wonder why this happens and can be a reason for my problem?
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply