SQL Server Agent has a built-in alerting process for when jobs fail, but the information it provides isn’t very useful. You’re only told which job, what time, who ran it, and which step failed. If you want to see why it failed, you have to review the job history manually. On a busy system with […]
2020-10-29
5,427 reads
2020-10-22
3,746 reads
2019-11-14
728 reads
Lists the job names and package names for jobs that execute SSIS packages (for packages stored in msdb).
2017-09-13 (first published: 2017-09-05)
772 reads
Finding the nightly job failures is just one of a DBA's morning rituals. It is fairly easy to scan all the email with a number of creative search criteria, but what if you would like a more automated approach? Read on to learn how to find and report all job failures using a script.
2017-01-12
4,563 reads
Your SQL Agent Jobs may be silently failing when using Linked Servers.
2016-05-02
1,883 reads
2016-04-28
1,423 reads
To show SQL Server and physical server details upon instance restart so that we have visibility of unexpected issues with servers and services.
2016-02-18 (first published: 2016-02-04)
592 reads
This script outputs sql server service, start type, status, Service Account, installation location, start up time, uptime of sql server related services along with startup trace flags.
2015-12-17 (first published: 2015-12-09)
1,076 reads
2015-11-10
1,606 reads
By Steve Jones
I was honored to speak at the WIT Mental Health and Wellness day last...
By Steve Jones
I started to add a daily coping tip to the SQLServerCentral newsletter and to...
I’ve talked about SQL Server comments before and how important they are. In PowerShell...
As there isn't an option to use a DDL trigger on a RESTORE query,...
Hi there I have two tables, one with an ID and Amount (Table 1)...
Comments posted to this topic are about the item The Gift of Asking Stupid...
Ask SSC