login auditing not writing to log

Hello,
I have turned on the login auditing in the server properties to log
both failed and successfull logins. I logged out and logged back in to
test the feature. However, the system did not write the login details
to the sql server log. Do I have to bounce the sqlserver?
Are DDL triggers the only way to turn on database auditing in SQL
Server 2005?
Regards
Jaideep
Yes, you need to bounce the SQL2000/2005 instance.
Linchi
"jai" wrote:

> Hello,
> I have turned on the login auditing in the server properties to log
> both failed and successfull logins. I logged out and logged back in to
> test the feature. However, the system did not write the login details
> to the sql server log. Do I have to bounce the sqlserver?
> Are DDL triggers the only way to turn on database auditing in SQL
> Server 2005?
> Regards
> Jaideep
>
|||Hello Jai,
For SQL 2000 or SQL 2005 after doing the change you need to stop and start
SQL Server service.
DDL trigger can be used to audit the schema changes. Say you can audit
alter, drop or create statements
into a table or fire an action you could use DDL triggers.
Thanks
Hari
"jai" <dbasybase@.gmail.com> wrote in message
news:1169496539.784616.88210@.m58g2000cwm.googlegro ups.com...
> Hello,
> I have turned on the login auditing in the server properties to log
> both failed and successfull logins. I logged out and logged back in to
> test the feature. However, the system did not write the login details
> to the sql server log. Do I have to bounce the sqlserver?
> Are DDL triggers the only way to turn on database auditing in SQL
> Server 2005?
> Regards
> Jaideep
>