Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have been trying to Google up an answer for this, but I can never seem to find the right answer.

I've been given the job of finding out how to lock out an account from SQL Server 2008(on Windows Server 2008 Standard SP2) after there's been so many number of login attempts. We're being hit with the SQL Slammer(or something similar) and I'm at my wits end trying to figure this out. I'm not a server guy in the slightest, and apparently neither is the guy who actually owns the server by the looks of how terribly setup the server and the applications that depend on it are setup.

  • I am not allowed to block port 1443. We have one application uses it and my boss doesn't want to make the one tiny company that uses it do a quick software update on a few computers to patch it up. He's said for the past month he's going to get the IP addresses of the employees that would need access so that we can block everyone except for them, but he's yet to come through with this.

  • I've been attempting to firewall the IP addresses that come up in the error logs, but this seems a bit futile to have to constantly check. Usually by the time I get the IP
    address, the attacker's already attempted several thousand login attempts.

  • I've already disabled the sa account.

  • I've already gone into the local security settings and set all of those(Account lockout duration = 30 minutes, account lockout threshold = 10 failed attempts)

  • The database's server authentication is set to SQL Server and Windows Authentication

I honestly don't know what to do. I'm assuming there's some sort of policy I can create for it, but that's entirely beyond my abilities at the moment.

share|improve this question
up vote 1 down vote accepted

Unfortunately you are in a bad place. We talked about this exact thing over here.

share|improve this answer
Looks like I'm pretty stuck. Thanks for the link! – Ross Oct 7 '09 at 21:18

SQL Server 2008 Enterprise Edition and above support the ability to set security policies which includes the ability to set lockout count and durations. Unfortunately, you are running standard.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.