Skip To Main Content
Where-object LastRunOutcome on Muck Rack

Where-object LastRunOutcome

As seen in: SQL Server Central
Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work. Claim your profile

Get in touch with Where-object

Contact Where-object, search articles and posts on X, monitor coverage, and track replies from one place.

Learn more about Muck Rack

Actions

Share this page

Is this you?

As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile

Articles

Failing SQL Agent Jobs – Part 2 – SQLServerCentral

|
By Convert To-Html, Where-object LastRunOutcome, No Schedule"
| SQL Server Central
Welcome to Part 2 in the series about SQL Server Agent Job Failures. In this part you are going to learn how to build an HTML report with Failed Agent Job information and send the report via e-mail to the interested team(s). Let’s get started putting the pieces together to build our report. First step: Picking up where we left off based on Part 1 of the series, the $servers variable is populated with all the SQL Servers you will be checking for Failed Agent Jobs.
Open in Who Shared Issue with article?

Failing SQL Agent Jobs – Part 1 – SQLServerCentral

|
By Where-object LastRunOutcome, Format-table SqlInstance
| SQL Server Central
SQL Server Agent Jobs are one of the core features of SQL Server. Agent Jobs perform many actions, from maintenance tasks (server and database), data movement flows, replication, log shipping, data cleanup, health checks and many more. Since Agent Jobs are a critical component in a data organization, it is important to know when Agent Jobs do not succeed. There are several ways to accomplish the monitoring of failed Agent Jobs, from easy to more complex.
Open in Who Shared Issue with article?
See all 2 articles