Post reply

Job history is missing.......

  • June 17, 2011 at 6:04 pm

    #242344

    Guys,

    In my SQLSERVER 2005 , A scheduled Job has been failed.. but the history about that not mentioned in <view job histroy>.

    how can i get the cause of failure of that job.

    Thanks and Regards,

    Sakthivel

  • June 18, 2011 at 7:33 am

    #1340782

    check the sqlagent log file (sqlagent.out) if it holds some info regarding your troublesome job.

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Need a bit of Powershell? How about this

    Who am I ? Sometimes this is me but most of the time this is me

  • June 20, 2011 at 5:54 am

    #1341097

    Also, check and see how often your job log clears itself out. That would be the reason why you're not seeing a history on the job.

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • June 20, 2011 at 12:32 pm

    #1341385

    Brandie Tarvin (6/20/2011)

    Also, check and see how often your job log clears itself out. That would be the reason why you're not seeing a history on the job.

    Yes, I find the default settings to be low, and I usually make them much higher.

  • June 20, 2011 at 2:19 pm

    #1341444

    homebrew01 (6/20/2011)

    Brandie Tarvin (6/20/2011)

    Also, check and see how often your job log clears itself out. That would be the reason why you're not seeing a history on the job.

    Yes, I find the default settings to be low, and I usually make them much higher.

    I actually turn them off in SQL Server Agent properties, and then implement a maintenance plan that run the History Cleanup task and set it for 6 months.

    This keeps 6 months of history available for all jobs, maintenance plans, backups, etc...

    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

  • June 21, 2011 at 12:48 am

    #1341640

    Are you executing the job first time?

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply