Patrick LeBlanc

All authors

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.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

(24)

You rated this post out of 5. Change rating

2007-10-10

15,330 reads

All authors

Blogs

PowerPoint to HTML with Claude AI

By

I had an idea for an animated view of a sales tool, and started...

Don’t Miss Out – SQL Server Query Tuning Fundamentals Starts Next Monday!

By

Next Monday, February 9, 2026, my one-day live online training SQL Server Query Tuning...

Monday Monitor Tips: SQL Auditing Preview

By

One of the features we advocates have been advocating for is a better way...

Read the latest Blogs

Forums

Tame Those Strings (Series)

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Tame Those Strings (Series)

SSRS shared dataset parameters not showing in expression builder

By SLL1966

I am creating shared datasets that our executive staff can use for creating reports...

SSRS shared dataset parameters not showing in expression builder

By SLL1966

I am creating shared datasets that our executive staff can use for creating reports...

Visit the forum

Question of the Day

The Decoded Value

In SQL Server 2025, what is returned from this code: 

DECLARE @message VARCHAR(50) = 'Hello SQL Server 2025!';
DECLARE @encoded VARCHAR(MAX);

SET @encoded = BASE64_ENCODE(CAST(@message AS VARBINARY(1000)));
SELECT BASE64_DECODE(@encoded)

See possible answers