Collecting the Information in the Default Trace

Posted on Simple Talk See other posts from Simple Talk
Published on Tue, 02 Jul 2013 00:00:00 GMT Indexed on 2013/07/02 17:11 UTC
Read the original article Hit count: 199

The default trace is still the best way of getting important information to provide a security audit of SQL Server, since it records such information as logins, changes to users and roles, changes in object permissions, error events and changes to both database settings and schemas. The only trouble is that the information is volatile. Feodor shows how to squirrel the information away to provide reports, check for unauthorised changes and provide forensic evidence.

© Simple Talk or respective owner

Related posts about Database Administration