January 22, 2014 at 2:23 pm
SQL Server Logs is filled with one specific failed login. I disabled the account, but the failed login still writes to the Logs. How can I prevent this? I don't want to disabled the failed logins feature on the server properties. Thank you.
January 22, 2014 at 3:34 pm
You need to prevent it from repeatedly trying to connect to SQL. this could even be a hacking attempt. The login failure message should give an ip address for the client, start there, talk to your sysadmins and\or security people
---------------------------------------------------------------------
January 22, 2014 at 3:52 pm
Thanks, George. I will talk to our system admin. but at the same time, since all the failed logins are recorded in the Error Logs, which makes it grows fast. Is there a way to prevent writing the specific failed logins to the Logs?
January 22, 2014 at 5:05 pm
other than the obvious you understandably don't want to use, I don't know of a way. There may be a trace flag to change this behaviour.
---------------------------------------------------------------------
January 23, 2014 at 2:50 am
You can prevent all failed logins from writing to the log, but not one specifically
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply