Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

Alert not working Expand / Collapse
Author
Message
Posted Monday, June 13, 2005 1:54 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, February 20, 2014 10:05 AM
Points: 287, Visits: 208

Has anyone figured this one out yet.  I'm having same problem. 

Trace flag is set

alert is enabled

I caused an error 1205 and did not receive the alert.






Curtis Smith
SQL Server DBA
Well in worked in Theory ...
Post #190112
Posted Tuesday, June 14, 2005 12:04 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 3:43 AM
Points: 7,005, Visits: 8,453

my 2ct

- did you stop and restart sqlagent _after_ you enabled the (first) alert ?

- also add traceflag 3605 for more deadlockinfo in the sqlservereventlog.

 



Johan


Don't drive faster than your guardian angel can fly ...
but keeping both feet on the ground won't get you anywhere

- How to post Performance Problems
- How to post data/code to get the best help


- How to prevent a sore throat after hours of presenting ppt ?


"press F1 for solution", "press shift+F1 for urgent solution"


Need a bit of Powershell? How about this

Who am I ? Sometimes this is me but most of the time this is me
Post #190196
Posted Tuesday, August 30, 2005 11:47 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Tuesday, February 26, 2008 6:48 PM
Points: 18, Visits: 20
Hello everyone ... has anyone found a resolution to this problem?
I get notified with other alerts i setup but not the Deadlock 1205 alert. Please advise.
Post #215393
Posted Tuesday, August 30, 2005 2:46 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, February 20, 2014 10:05 AM
Points: 287, Visits: 208
I was the original post.  If I remember correct this is a documented problem is Sql Server.  Stop and restart the SQL Server and the problem is corrected.




Curtis Smith
SQL Server DBA
Well in worked in Theory ...
Post #215461
Posted Tuesday, August 30, 2005 4:19 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Tuesday, February 26, 2008 6:48 PM
Points: 18, Visits: 20
Hi Curtis,

Thanks for the reply. I can't seem to find it in Microsoft's site. I'll keep searching. Would it be possible to point me to the right direction on seaching for this document.

Thanks again.

Steve
Post #215485
Posted Wednesday, August 31, 2005 8:26 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, February 20, 2014 10:05 AM
Points: 287, Visits: 208

found two articles.  the first is the MS article I found.  THe problem described is not the same problem. but the behavior is the same.  The second is an atricle about deadlocks and the author states that you must start or restart the sql server.

I did a lot of testing on this ad the final solution was to restart the SQL Server.  I think I reset up the Alert and restated the SQL Server.

http://support.microsoft.com/kb/q239753/

http://www.databasejournal.com/features/mssql/article.php/1498781

 






Curtis Smith
SQL Server DBA
Well in worked in Theory ...
Post #215703
Posted Wednesday, August 31, 2005 8:50 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Monday, September 27, 2010 3:05 PM
Points: 1,629, Visits: 62

This is similar to this post

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=5&messageid=215490

Is this a secret double life?




Post #215713
Posted Wednesday, August 31, 2005 8:57 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Monday, September 27, 2010 3:05 PM
Points: 1,629, Visits: 62

don't need trace flag 3605, just need 1204

Try this to set the alert up:

        EXEC dbo.sp_add_alert 'Error 1205 - Deadlock detected', 1205, 0, 1, 60, NULL, 5
        EXEC dbo.sp_add_notification 'Error 1205 - Deadlock detected', 'whoever', 5

This works for me...




Post #215718
Posted Wednesday, August 31, 2005 12:37 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Tuesday, February 26, 2008 6:48 PM
Points: 18, Visits: 20
Thanks so much guys!

The restart definitely resolved the problem. A restart is usually not an option in my shop unless to resolve a problem even with dev/test servers =(.
Post #215843
Posted Wednesday, April 9, 2014 3:09 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, May 1, 2014 6:21 PM
Points: 1, Visits: 34
confirm these, hope this will help

1. DBCC TRACESTATUS
2. Go to sql agent properties\ Alert System and Enable mail profile

Post #1560195
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse