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,832 reads
2020-10-22
4,644 reads
2019-11-14
729 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)
799 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,937 reads
2016-04-28
1,425 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)
598 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,084 reads
2015-11-10
1,608 reads
By Steve Jones
I started to add a daily coping tip to the SQLServerCentral newsletter and to...
In my last post I talked about invoke-sqlcmd. It’s a nice easy way to...
By Rayis Imayev
(2021-Sep-21) There is one scene in "The Core" movie that I really like when two geophysicists...
I'm currently interested in self-hosting and I recognized that mostly it's about alternatives for...
Hi all. I have also posted this on DBA Stack Exchange, but I'm posting...
I have been asked to revoke access from a few developers in SQL Server...
Ask SSC