﻿<?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, Naming Standards, Basics</title><link>http://www.sqlservercentral.com/</link><description>Content tagged Database Design, Naming Standards, Basics posted on SQLServerCentral.com</description><language>en-us</language><ttl>360</ttl><managingEditor>sjones@sqlservercentral.com (Steve Jones)</managingEditor><item><title>A Lookup Strategy Defined</title><description>Most databases designs nowadays seem to have at least a few if not many lookup or reference tables. This article helps you define a strategy in how to design, approve, and deploy them.
</description><guid>http://www.sqlservercentral.com/articles/Basics/lookupstrategy/921/</guid><pubDate>2003/02/20</pubDate><link>http://www.sqlservercentral.com/articles/Basics/lookupstrategy/921/</link></item><item><title>Using Uniqueindentifier Instead of Identity</title><description>Identity columns are last years news. Have you experimented with uniqueindentifiers - better known to programmers as GUID&amp;#39;s? Guaranteed to be unique in the world, they offer a powerful alternative to identity columns.

</description><guid>http://www.sqlservercentral.com/articles/Basics/usinguniqueindentifierinsteadofidentity/439/</guid><pubDate>2001/09/17</pubDate><link>http://www.sqlservercentral.com/articles/Basics/usinguniqueindentifierinsteadofidentity/439/</link></item></channel></rss>