If you haven’t migrated your workloads to a managed database platform yet, you’re probably still relying on SQL Server Agent for various maintenance and other scheduled tasks. Most of the time, these processes just work. But when it’s time to troubleshoot, it can be cumbersome to get to the root of some problems.
2024-04-17
This script will create the necessary login and linked servers on a given availability replica. Please ensure that the script is executed on all the replicas.
2022-02-22 (first published: 2022-01-25)
7,816 reads
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
7,859 reads
2020-10-22
9,365 reads
2019-11-14
762 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)
2,015 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
2,753 reads
2016-04-28
1,459 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)
742 reads
By Brian Kelley
But as I've matured over the years, I came to realize that I needed...
By alevyinroc
I will be presenting my latest session, Documenting Your Work for Worry-Free Vacations, in-person...
By Steve Jones
I saw a question asking about the next sequence value and decided to try...
I've read a few posts regarding what we use to design DB models and...
I've got a table with 186,703,969 rows, about 300GB of data. There are several...
I created a SQL Database in Azure Portal but I've just noticed it also...
What values are returned when I run this code?
CREATE TABLE dbo.IdentityTest2
(
id NUMERIC(10,0) IDENTITY(10,10) PRIMARY KEY,
somevalue VARCHAR(20)
)
GO
INSERT dbo.IdentityTest2
(
somevalue
)
VALUES
( 'Steve')
, ('Bill')
GO
SELECT top 10
id
FROM dbo.IdentityTest2 See possible answers 