<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Sarbanes-Oxley on SQL Server 2005 </title><link>http://blogs.technet.com/james/archive/2006/05/22/429815.aspx</link><description>I've just finished reading an interesting article on a DBA who used some of the new features in SQL Server 2005 to implement their auditing strategy so that they are compliant with Sarbanes-Oxley. Auditing is often seen as a pain, and it is. It's one</description><dc:language>en-GB</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Interesting Finds: May 22, 2006 PM edition</title><link>http://blogs.technet.com/james/archive/2006/05/22/429815.aspx#429842</link><pubDate>Tue, 23 May 2006 02:43:52 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:429842</guid><dc:creator>Jason Haley</dc:creator><description /></item><item><title>Interesting Finds: May 22, 2006 PM edition</title><link>http://blogs.technet.com/james/archive/2006/05/22/429815.aspx#429843</link><pubDate>Tue, 23 May 2006 02:44:48 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:429843</guid><dc:creator>Jason Haley</dc:creator><description /></item></channel></rss>