﻿<?xml version="1.0" encoding="utf-8"?><rss xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="2.0"><channel><title>SQLServerCentral.com Content tagged Administration, SQL Server 2005, Database Design</title><link>http://www.sqlservercentral.com/</link><description>Content tagged Administration, SQL Server 2005, Database Design posted on SQLServerCentral.com</description><language>en-us</language><ttl>360</ttl><managingEditor>sjones@sqlservercentral.com (Steve Jones)</managingEditor><item><title>Using SQL Server 2005 to document Sarbanes-Oxley compliance</title><description>My CIO and I have looked at a number of commercial solutions for documenting Sarbanes-Oxley compliance. However, we decided to use SQL Server 2005&amp;#39;s built-in tools to create our own &amp;#34;home-grown&amp;#34; auditing system.


</description><guid>http://www.sqlservercentral.com/redirect/articles/2414/</guid><pubDate>2006/05/19</pubDate><link>http://www.sqlservercentral.com/redirect/articles/2414/</link></item></channel></rss>