• Jeff Moden (4/22/2016)


    Welsh Corgi (4/22/2016)


    Lowell (4/22/2016)


    check to see how long your history retention is; it could easily have been written, but aged out by the time you look at it.

    if it is still a the server default, failed job steps could easily be pushed out/aged due to other job steps(ie LOG backups ever 15 minutes,for 100 database,s is 1500 messages, 500 more than the 1K default.

    I just created the job yesterday.

    There is an entry for the job and the step but the only information that I get is that the step failed.

    Thanks.

    If you go to the "advanced" tab there within each step of the job, I believe you might find the option to "Include Step Output to Log" for future debugging purposes. Can't say for sure for SSIS steps because I avoid SSIS whenever I can and have been successful at that for quite a while. 😀

    Thank you Sir.

    For better, quicker answers on T-SQL questions, click on the following...
    http://www.sqlservercentral.com/articles/Best+Practices/61537/

    For better answers on performance questions, click on the following...
    http://www.sqlservercentral.com/articles/SQLServerCentral/66909/