External Article

SQL Server Agent Jobs without an Operator

I work in a fairly large and unwieldy SQL Server shop. Our environment is the wild west. I have DBAs and Developers on my team that create SQL Server Agent Jobs all of the time and there is never an operator setup to email anyone based on a failure condition. I know the right solution here is to "tame the wild west" by locking down the environment and setting up a change management process, but I think that is a topic for another day. Can you give me some idea of how to identify the new recently created SQL Server Agent Jobs and Jobs without an operator setup to email us for a failure condition? I would like to receive emails when either of these conditions occur. Check out the solution to this tip to learn how.

Blogs

How AgentDBA Identifies Backup Failures

By

Every DBA has a box like this. Sitting untouched for months. Nobody’s proud of...

Tip: Expanding a SQL statement

By

In all recent versions of the database you can call DBMS_UTILITY.EXPAND_SQL_TEXT to get the...

AI Helps Me with My Sloppiness

By

I type fairly well. Well, I type fast, but I do wear out a...

Read the latest Blogs

Forums

From SQL Server On-Premises to Claude Desktop: How I built a Full MCP Pipeline

By Cláudio Tereso

Comments posted to this topic are about the item From SQL Server On-Premises to...

Independence Day 2026

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Independence Day 2026

Independence Day 2026

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Independence Day 2026

Visit the forum

Question of the Day

Independence Day 2026

In the original Independence Day movie (1996), what type of computer did Jeff Goldblum use to connect to the alien mainframe? Take a guess, don't look it up or ask AI.

See possible answers