﻿<?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 T-SQL, Auditing</title><link>http://www.sqlservercentral.com/</link><description>Content tagged T-SQL, Auditing posted on SQLServerCentral.com</description><language>en-us</language><ttl>360</ttl><managingEditor>sjones@sqlservercentral.com (Steve Jones)</managingEditor><item><title>Audit data using SQL Server 2005's COLUMNS_UPDATED function</title><description><![CDATA[<p>Auditing data changes in your production environment is very important, especially if you are dealing with confidential information.</p>]]></description><guid>http://www.sqlservercentral.com/redirect/articles/64669/</guid><pubDate>Thu, 23 Oct 2008 06:00:00 UT</pubDate><link>http://www.sqlservercentral.com/redirect/articles/64669/</link></item><item><title>SqlCredit – Part 17: Exploring SQL 2005’s OUTPUT Clause</title><description><![CDATA[<p>SQL Server 2005 introduces the OUTPUT clause, a bit of magic that allows us to get the identity value, plus a number of other values, from an INSERT, UPDATE, or DELETE, which all have different interaction with OUTPUT. This article concentrates on INSERT.</p>]]></description><guid>http://www.sqlservercentral.com/redirect/articles/63892/</guid><pubDate>Mon, 04 Aug 2008 06:00:00 UT</pubDate><link>http://www.sqlservercentral.com/redirect/articles/63892/</link></item></channel></rss>