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.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

4.38 (24)

You rated this post out of 5. Change rating

2007-10-10

15,316 reads

All authors

Blogs

Local LLM Models at SQL Saturday Boston 2025

By

I’m starting a long trip at Boston this weekend. I’ll be there Saturday speaking,...

3 things you must do to start data quality management right

By

As a data & AI strategist who’s seen countless projects succeed and fail, I...

Set Theory vs. Batch Mode in SQL Server

By

Set Theory vs. Batch Mode in SQL Server Not long ago,...

Read the latest Blogs

Forums

Changing the Recovery Time

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Changing the Recovery Time

Getting More Time from AI

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Getting More Time from AI

When Page Prefetching Takes a Back Seat – Exploring Trace Flag 652 in SQL Server

By Chandan Shukla

Comments posted to this topic are about the item When Page Prefetching Takes a...

Visit the forum

Question of the Day

Changing the Recovery Time

I want to change the recovery time for a database running on SQL Server 2022. What are my options for setting the value in my ALTER DATABASE statement. If I run this code, what can I use in place of the xxx to define what 12 means? 

ALTER DATABASE Finance 
 SET TARGET_RECOVERY_TIME = 12 xxx;

See possible answers