Please start any new threads on our new site at We've got lots of great SQL Server experts to answer whatever question you can come up with.

Our new SQL Server Forums are live! Come on over! We've restricted the ability to create new threads on these forums.

SQL Server Forums
Profile | Active Topics | Members | Search | Forum FAQ
Register Now and get your question answered!
Save Password
Forgot your Password?

 All Forums
 Site Related Forums
 Article Discussion
 Article: Alerts for when Logins Failures Strike
 Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

Ask SQLTeam Question

0 Posts

Posted - 07/16/2008 :  07:54:24  Show Profile  Visit AskSQLTeam's Homepage  Reply with Quote

When repeated SQL Server login failures occur, a DBA should investigate. It could just be someone repeatedly typing in the wrong password. Worst case is a virus attack flooding your network with connection requests. Receiving an e-mail while login failures are occurring allows DBAs to investigate and fix the issue as soon as possible. So how is DBA notified of login failures without flooding their inbox?

Read Alerts for when Logins Failures Strike

Starting Member

1 Posts

Posted - 08/04/2008 :  10:42:36  Show Profile  Reply with Quote
Another cause for failed login attempts is due to a CPU timing issue on multiprocessor and multi-core servers. The resolution is to add /usepmtimer to boot.ini.

This is applicable to both Intel and AMD processors.
Go to Top of Page

Starting Member

9 Posts

Posted - 04/15/2009 :  11:37:45  Show Profile  Reply with Quote
i have something similar but on a longer lag. when there is a failed login it writes event id 18456 to the app log. on win2003 and higher servers i was going to write a powershell script to check for this and alert me every time it happens
Go to Top of Page

Starting Member

1 Posts

Posted - 05/06/2009 :  09:14:41  Show Profile  Reply with Quote
"Msg 207, Level 16, State 1, Procedure usp_AlertLoginFailed, Line 79
Invalid column name 'Last_Occurrence_date'."

I've run these scripts on several of my SQL boxes and have had great success, however, this error occurs on two of them. I'm a pretty green DBA, so any help/insight would be helpful. :)
Go to Top of Page
  Previous Topic Topic Next Topic  
 Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.02 seconds. Powered By: Snitz Forums 2000