Installing SQL Server Agent on Ubuntu Server

Manvendra Singh explains how to install SQL Server Agent on an Ubuntu server, so that you can create SQL Server Agent Jobs to schedule repetitive tasks.

SQL server Agent - Status

As part of the application to monitor SQL health I created.
The procedure returns status of the SQL server Agent

Monitoring Longest Running Transaction using SQL Server Agent Alerts

Step by Step guide to setup SQL Server Agent Alert for the proactive monitoring of Monitoring of Longest Running Transactions.

Automating SQL Server Agent Notification

This article looks at some automated approaches of monitoring SQL Server agent jobs.

Setting Up Your SQL Server Agent Correctly

It is important to set up SQL Server Agent Security on the principles of 'executing with minimum privileges’, and ensure that errors are properly logged and alerts are set up for a comprehensive range of errors. SQL Server Agent allows fine-grained control of every job step that should allow tasks to be run entirely safely even if they occasionally need special privileges.

Querying SQL Server Agent Job History Data

Often times we are tasked with having to programmatically come with a list of durations per SQL Server Agent Job to trend the run times and order the results by date. Unfortunately it's not always easy in the way the data is stored in the system tables in the MSDB database. This tip explains how to use the system tables to get the data into the correct format for dates and job durations.

Never update systems tables directly - a study in Agent job scheduling

It is often recommended that system tables should not be updated directly. Presenting a case in point built around nightly job configuration in order to demonstrate the possible issues with updating system tables directly.

Querying SQL Server Agent Job Information

Is there an easy/automated way to get information on SQL Server Agent jobs instead of connecting to each server and manually getting the information through the SSMS GUI?

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.

SQL Server Job Steps