Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2008-07-16 : 07:54:24
|
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 |
|
|
rklimaszewski
Starting Member
1 Post |
Posted - 2008-08-04 : 10:42:36
|
| 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.http://www.tek-tips.com/viewthread.cfm?qid=1450507&page=1 |
 |
|
|
sql_noob
Starting Member
9 Posts |
Posted - 2009-04-15 : 11:37:45
|
| 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 |
|
|
|
landoawd
Starting Member
1 Post |
Posted - 2009-05-06 : 09:14:41
|
| "Msg 207, Level 16, State 1, Procedure usp_AlertLoginFailed, Line 79Invalid 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. :) |
|
|
|
|
|
|
Article: Alerts for when Logins Failures Strike