﻿<?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 Database Design, Auditing</title><link>http://www.sqlservercentral.com/</link><description>Content tagged Database Design, Auditing posted on SQLServerCentral.com</description><language>en-us</language><ttl>360</ttl><managingEditor>sjones@sqlservercentral.com (Steve Jones)</managingEditor><item><title>Designing Tables for Audit Data in SQL Server</title><description>My company is just starting to look at adding functionality to retain historical data for key tables and columns for auditing purposes in many of our SQL Server databases.  I have seen some of your recent tips related to triggers (Forcing Trigger Firing Order in SQL Server and Trigger Alternatives in SQL Server - OUTPUT Clause).  Based on using triggers or a similar technology, what is the best way to store the historical data?</description><guid>http://www.sqlservercentral.com/redirect/articles/62769/</guid><pubDate>2008/04/15</pubDate><link>http://www.sqlservercentral.com/redirect/articles/62769/</link></item></channel></rss>