Re: SQL 2000 Lockout?
- From: "zz12" <IDontLikeSpam@xxxxxxxxxxx>
- Date: Tue, 29 Apr 2008 11:43:40 -0700
Yes we do have audit logs and monitor the Failed Attempts but just was
wondering if someone knew if there was something out there along those lines
like I mentioned earlier. Thanks for your reply RLF much appreciated though
:-)
"Russell Fields" <russellfields@xxxxxxxxxx> wrote in message
news:e6$iMu%23pIHA.4928@xxxxxxxxxxxxxxxxxxxxxxx
zz12,
With SQL Server 2000, there is nothing native to do this. If someone else
has code to do this I don't remember who they are any more.
If you server is set to Audit Failed Logins, these entries will go into
your event logs and you could write some code to periodically scan the
event log. (Not the same as automatic lockout, of course, but it is
something.)
RLF
"zz12" <IDontLikeSpam@xxxxxxxxxxx> wrote in message
news:%23QDyj%23vpIHA.3616@xxxxxxxxxxxxxxxxxxxxxxx
Hello, would anyone know if there's a way to lockout mainly a SQL (or
Windows) login for SQL Server 2000? Was wondering if there was like a
stored procedure out there that could be added to the Master db running
as a system process that checks for like 3 failed login attempts or
something along those lines.
Thanks in advance.
.
- References:
- SQL 2000 Lockout?
- From: zz12
- Re: SQL 2000 Lockout?
- From: Russell Fields
- SQL 2000 Lockout?
- Prev by Date: Re: What type of Server Roles to assign for Backup and Recovery
- Next by Date: Re: What type of Server Roles to assign for Backup and Recovery
- Previous by thread: Re: SQL 2000 Lockout?
- Next by thread: Granting EXEC for read only SPs
- Index(es):
Relevant Pages
|