Scheduled Job History

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • P.D.N. Tame

    Scheduled Job History

    Is there a way to increase the number of records preserved in job
    history? I have 82 jobs on my box, 30 of them run every 20 minutes
    for 23 hours a day, every 30 days. Another 30 run once, every 30
    days. The system seems to have a limit of 50 history records for any
    job that hasn't run since yesterday and purges all history records if
    the job is more than a week old. I didn't know if there might be a
    configuration record buried in MSDB or somewhere else that would allow
    me to increase this size or perhaps a system SP that prunes job
    history that I could modify.

    It isn't critical as the system is set to notify me when jobs fail,
    but still, I'd like to be able to look at a given day and verify that
    everything went normally.
  • Simon Hayes

    #2
    Re: Scheduled Job History


    "P.D.N. Tame" <wwphx@hotmail. com> wrote in message
    news:bcc5d277.0 312090628.5061b 581@posting.goo gle.com...[color=blue]
    > Is there a way to increase the number of records preserved in job
    > history? I have 82 jobs on my box, 30 of them run every 20 minutes
    > for 23 hours a day, every 30 days. Another 30 run once, every 30
    > days. The system seems to have a limit of 50 history records for any
    > job that hasn't run since yesterday and purges all history records if
    > the job is more than a week old. I didn't know if there might be a
    > configuration record buried in MSDB or somewhere else that would allow
    > me to increase this size or perhaps a system SP that prunes job
    > history that I could modify.
    >
    > It isn't critical as the system is set to notify me when jobs fail,
    > but still, I'd like to be able to look at a given day and verify that
    > everything went normally.[/color]

    In Enterprise Manage, right-click SQL Server Agent, then pick Properties,
    Job System, and set the history options as you want. You can also use
    sp_set_sqlagent _properties, but this procedure isn't documented, so it may
    not be the best way to go.

    Simon


    Comment

    Working...