Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

Sql jobs on some servers not saving history

Posted on 2006-07-12
5
Medium Priority
?
368 Views
Last Modified: 2006-11-18
I have multiple SQL servers that all run SQL jobs routinely. The jobs on one of the servers are saving NO job history despite the fact that the jobs were all inserted using the same script. Is there a setting particular to the instances of SQL server that controls this? I am trying to troubleshoot some job issues and without any history it is hard to tell what the issue is. The check box to "append output to step history" in the advanced properties of "edit job step" is not checked for both jobs that are recording history and for those that are not.
Thank You!
0
Comment
Question by:Tommy Jackson
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 12

Expert Comment

by:Einstine98
ID: 17096390
right click on the sql agent and go to job system and you can set the history settings there.
0
 

Author Comment

by:Tommy Jackson
ID: 17096411
The settings are the same for all servers. They are set to "limit size" to 1,000 maximum job history rows and 100 maximum job histroy rows per job.
0
 
LVL 12

Accepted Solution

by:
Einstine98 earned 2000 total points
ID: 17096432
if you have more than 10 jobs then maybe some overwriting is taking place, run the job manually and immediately check the history,is it there?
0
 

Author Comment

by:Tommy Jackson
ID: 17096454
I ran one this afternoon and it did create history. This particular server does have 3 databases and thus 3 times the jobs as many others. I have changed the max rows to 4,000 and stopped/started the agent. I'll know in the morning when all of the jobs have run. It does seem likely to be the issue. More in the morning.
0
 

Author Comment

by:Tommy Jackson
ID: 17098472
Expanding the maximum number of rows allowed for SQL job history did the trick for having history for the jobs. All jobs have history this morning. Thank you for your help!
0

Featured Post

Ask an Anonymous Question!

Don't feel intimidated by what you don't know. Ask your question anonymously. It's easy! Learn more and upgrade.

Question has a verified solution.

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

Why is this different from all of the other step by step guides?  Because I make a living as a DBA and not as a writer and I lived through this experience. Defining the name: When I talk to people they say different names on this subject stuff l…
In this article we will learn how to fix  “Cannot install SQL Server 2014 Service Pack 2: Unable to install windows installer msi file” error ?
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.
Viewers will learn how to use the SELECT statement in SQL to return specific rows and columns, with various degrees of sorting and limits in place.

609 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