<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.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>Light weight SQL Server procedure auditing without using SQL Server auditing</title><link>http://blogs.msdn.com/jenss/archive/2009/06/08/light-weight-sql-server-procedure-auditing-without-using-sql-server-auditing.aspx</link><description>A week ago a colleague asked for different options to do audit stored procedure calls. With his allowance I will post the question here. “The applications used at the customer site all access these databases using stored procedures ( only , as far as</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator></channel></rss>