• John Mitchell-245523 (8/15/2016)


    Jeff

    Does your job highlight just jobs that failed, or does it include those that didn't run, perhaps because they were accidentally disabled, or because SQL Server Agent wasn't running?

    I think backups are important enough to have their own report. Not only do I check that each database has been backed up, but also that the backup file exists in the location it was made.

    I'm not saying this to claim that my way of doing things is better, but just to point out that different thinks work for different people and in different circumstances.

    John

    The report shows a whole lot even for a "summary". It shows whether the job is currently enabled or not. It shows whether it's scheduled or not or if it's a "One time" job that's run manually on occasion, all highlighted in different colors if out of the norm of enabled and scheduled. It shows the number of times the job ran, how many were successful, how many failed (color highlighted on failure, of course), and how many were cancelled. It shows the earliest run date/time in the 24 hour period, the latest run date/time 24 hour period be damned and, if that is more than a week old, highlights it in Yellow and Red if it hasn't run in a month. It shows the min and max run durations and it shows the last time the job was changed. If it changed anytime in the last week, that date is also colorized. Of course, the addition of a job is a change.

    About the only thing not on the report is the median and mode of the run times and deleted jobs. And, like I said, I don't have a huge number of servers so each server generates it's own. It's an easy thing to push out to each server because I don't want all of the servers to stop reporting if the server that generates an enterprise wide report goes down..

    That being said, a report for backups isn't a bad idea. I just don't need it for the way we're setup. If that changes, then you can bet I'll have a report on backups to go along with the alerts. You can also bet that it WON'T be a PoSh script that does it and that it'll get pushed to each server, like the jobs reports I have.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)