<![CDATA[Latest Content by Larry Clark]]>http://www.sqlmag.com/authors/author/author/5777862/rss/5777862en-USFri, 25 May 2012 09:28:03 GMTFri, 25 May 2012 09:28:03 GMT<![CDATA[Get Compliant with SQL Server 2005 Audit Logging]]>http://www.sqlmag.com/article/auditing/get-compliant-with-sql-server-2005-audit-loggingHelp meet compliance goals by using SQL Trace, SQL Server Profiler, and C2 audit mode. View stored procedure examples that demonstrate audit logging with these features, and take a brief look at SQL Server 2008 auditing and third-party options.]]>Larry ClarkTue, 29 Apr 2008 00:00:00 GMThttp://www.sqlmag.com/article/auditing/get-compliant-with-sql-server-2005-audit-logging<![CDATA[Third-Party Audit-Logging Options]]>http://www.sqlmag.com/article/auditing/third-party-audit-logging-optionsThird-party transaction-log analyzers and gateways can audit logs and process and filter SQL Server traffic. They can analyze backup logs and use listener agents to collect and process SQL Server traffic to filter out the good stuff.]]>Larry ClarkTue, 29 Apr 2008 00:00:00 GMThttp://www.sqlmag.com/article/auditing/third-party-audit-logging-options<![CDATA[Common Criteria Compliance]]>http://www.sqlmag.com/article/auditing/common-criteria-complianceCommon Criteria Compliance is an advanced configuration option available in SQL Server 2005 SP1 (SP2 is under review). Government, military, financial, and other entities with serious security needs may require its certification and implementation.]]>Larry ClarkTue, 29 Apr 2008 00:00:00 GMThttp://www.sqlmag.com/article/auditing/common-criteria-compliance