SQLServerCentral Article

Deadlock Notifications in SQL Server 2005

Deadlocks do not occur too often, but when they do, it can be a time consuming and frustrating endeavor to track them down. In SQL Server 2000, you could alter the message to ensure these were written to the error log and track them down quickly. In SQL Server 2005, it is a little more tricky, but new author Patrick Leblanc brings us a technique for sending out a notification.

Blogs

Red Flags in Your Query (T-SQL Tuesday #200)

By

When I'm looking at a query, I bet it's bad if I see... a...

T-SQL Tuesday #200: When I Look at a Query …

By

This month is a milestone for T-SQL Tuesday. It’s number 200, which doesn’t sound...

Reflections on the Life of a DBA

By

The DBA life is fraught with pain. Those battles that we endure are mostly...

Read the latest Blogs

Forums

A Quick Second Opinion

By Steve Jones - SSC Editor

Comments posted to this topic are about the item A Quick Second Opinion

Five Intelligent Query Processing Features in SQL Server 2022 That Quietly Tune Your Workload

By vgupta

Comments posted to this topic are about the item Five Intelligent Query Processing Features...

Checking the Error Log I

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Checking the Error Log I

Visit the forum

Question of the Day

Checking the Error Log I

On my SQL Server 2025, I want to search the error log from my T-SQL code for potential issues and then inform an administrator. What is the current way to easily query the error log?

See possible answers