Patrick LeBlanc


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,171 reads

Blogs

The Community is YOU, Not Any Organization

By

As I type this, we’re leaving behind spring, and all the amazing events that...

Polyglot Persistence

By

I’ve seen the term polyglot persistence floating around Redgate a bit recently in the...

Six Months!

By

Oh good gosh. Six months without a single blog post. Most important information: I’m...

Read the latest Blogs

Forums

Dropping a Logon Trigger

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Dropping a Logon Trigger

SQL Injection Is Not Acceptable

By Steve Jones - SSC Editor

Comments posted to this topic are about the item SQL Injection Is Not Acceptable

Unzipping Word Documents in T-SQL

By cmartel 20772

Comments posted to this topic are about the item Unzipping Word Documents in T-SQL

Visit the forum

Question of the Day

Dropping a Logon Trigger

I created this trigger for testing on SQL Server 2022:

CREATE TRIGGER checksteve
ON ALL SERVER 
FOR LOGON  
AS  
BEGIN  
IF ORIGINAL_LOGIN()= N'ARISTOTLE\Steve'
 PRINT 'Steve logged in'
END;  
GO
Now I want to drop it. What do I run?

See possible answers