Hi.
I'm thinking of using the Auditing functions in SQL Server to record both successful and failed logon attempts to the application event log (this is as a short term solution until we implement Active Directory and Windows Authentication next year).
I've had a brief play with this and it seems to work OK. Has anyone else tried it in anger and have any comments about how it works (e.g. does it effect performance? take up loads of processer power? bloat the log files? etc.)
Also, I'll need to produce various reports from this - logons over time, persistent failed logons, etc. Can anyone recommend any third-party product to help with this? (I'd prefer not have to write my own!)
Finally, something we are keen on doing is revoking/disabling user accounts/alerting our Access Control team if they make three failed logon attempts. Any ideas of how this can be automated??
FYI: Running on SQL Server 2000 Standard edition, with Service Pack 3, running on Windows NT 4 SP6a boxes. The app is a realtime (24/7) mutual fund dealing and registration system, with upto 500 concurrent users (across several sites). The largest database size is around 100gigs, and we have about 200 servers any solution would need to be installed on.
Thanks in advance for any help,
Richard
I'm thinking of using the Auditing functions in SQL Server to record both successful and failed logon attempts to the application event log (this is as a short term solution until we implement Active Directory and Windows Authentication next year).
I've had a brief play with this and it seems to work OK. Has anyone else tried it in anger and have any comments about how it works (e.g. does it effect performance? take up loads of processer power? bloat the log files? etc.)
Also, I'll need to produce various reports from this - logons over time, persistent failed logons, etc. Can anyone recommend any third-party product to help with this? (I'd prefer not have to write my own!)
Finally, something we are keen on doing is revoking/disabling user accounts/alerting our Access Control team if they make three failed logon attempts. Any ideas of how this can be automated??
FYI: Running on SQL Server 2000 Standard edition, with Service Pack 3, running on Windows NT 4 SP6a boxes. The app is a realtime (24/7) mutual fund dealing and registration system, with upto 500 concurrent users (across several sites). The largest database size is around 100gigs, and we have about 200 servers any solution would need to be installed on.
Thanks in advance for any help,
Richard
