External Article

Setting Up Email Notification for SSIS Package Failure

As a DBA, we often setup monitoring to receive job failure notification, but when it comes to SSIS packages, we either do not capture the job failure (if the job runs through the command prompt) or we have no idea why it failed. In this article, I'd like to walk you through how to enable the logging functionality for SQL Server Integration Services (SSIS) and how to capture detailed information for immediate troubleshooting without "re-run" the package.

SQLServerCentral Editorial

A Leader

Today's editorial was originally reprinted on Jun 17, 2007. It is being re-run as it is a holiday in the US. Today Steve Jones looks at Jonthan Schwartz, the former CEO of SUN who took over from the founder, Scott McNealy.

Blogs

Upgrading SQL Server Containers on the Laptop

By

I don’t have SQL Server installed on my laptop. In an effort to keep...

How to Find Expensive Queries in Amazon Redshift

By

Slow-running queries can degrade your Redshift cluster’s performance and lead to increased costs. Identifying...

The Notification Trap: How Input Fatigue Is Killing Deep Work in Tech

By

If you've been here before, you know this blog is usually about SQL Server,...

Read the latest Blogs

Forums

SQL 2019 instance with AG, across 2 Windows 2016 OS servers - OSin-place upgrade

By millardus

Hi all Can I get some perspective from the community please on performing in-place...

How Long is a Long I/O?

By Steve Jones - SSC Editor

Comments posted to this topic are about the item How Long is a Long...

T-SQL Trigonometric Functions in SQL Server

By Imran2629

Comments posted to this topic are about the item T-SQL Trigonometric Functions in SQL...

Visit the forum

Question of the Day

How Long is a Long I/O?

In SQL Server 2025, a long I/O is recorded in the error log with message 833. How long much an I/O request be outstanding before this message is written to the log?

See possible answers