Modifying registry information to change type of login logging

[byrocat]

I've got a scratch databse that's gone into a production mode. One of
the things that our standards call for is that we log and monitor all
login failures.

In playing around with the server in the past, I've deleted some of
the system stored procedures (including those that deal with writing
the registry information.)

I probably could backup the database, force a new installation and
then restore and fix the databases, but this is a major impact on my
time.

Is it possible, and which registry keys do I need to update to enable
"login failures" to being set?

Thanks...

[Erland Sommarskog]

Re: Modifying registry information to change type of login logging

byrocat (strikemaster20 00@yahoo.ca) writes:

I've got a scratch databse that's gone into a production mode. One of
the things that our standards call for is that we log and monitor all
login failures.
>
In playing around with the server in the past, I've deleted some of
the system stored procedures (including those that deal with writing
the registry information.)
>
I probably could backup the database, force a new installation and
then restore and fix the databases, but this is a major impact on my
time.
>
Is it possible, and which registry keys do I need to update to enable
"login failures" to being set?

Which version of SQL Server do you use? If you have access to Management
Studio from SQL 2005, then click the buttons you need in the GUI, and
then select the Script option to see what SSMS would send to the server.
That should give you a clue.

If you have SQL 2000 and only the SQL 2000 tools, perform the same actio,
but use Profiler to spy on EM.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarsk og.se

Books Online for SQL Server 2005 at

http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx

Books Online for SQL Server 2000 at

http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx