﻿<?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, Best and Worst Practices</title><link>http://www.sqlservercentral.com/</link><description>Content tagged Database Design, Best and Worst Practices posted on SQLServerCentral.com</description><language>en-us</language><ttl>360</ttl><managingEditor>sjones@sqlservercentral.com (Steve Jones)</managingEditor><item><title>Best Practices in an Adhoc Environment</title><description>This short article looks at some mistakes developers should avoid when they also have the task of designing the database, database objects, or TSQL used to access it.
</description><guid>http://www.sqlservercentral.com/articles/Miscellaneous/bestpracticesinanadhocenvironment/1228/</guid><pubDate>2003/12/16</pubDate><link>http://www.sqlservercentral.com/articles/Miscellaneous/bestpracticesinanadhocenvironment/1228/</link></item><item><title>Worst Practice - Defining Rows that Exceed The Max Length</title><description>Andy started writing about worst practices a long time ago and returns this week with one that is short and sweet - why defining rows that exceed 8060 characters is a very bad idea and how you can avoid it.

</description><guid>http://www.sqlservercentral.com/articles/Miscellaneous/worstpracticedefiningrowsthatexceedthemaxlength/1179/</guid><pubDate>2003/12/08</pubDate><link>http://www.sqlservercentral.com/articles/Miscellaneous/worstpracticedefiningrowsthatexceedthemaxlength/1179/</link></item><item><title>SQL Server Database Coding Conventions and Best Practices</title><description>Learn the key basics of writing quality Transact-SQL code.
</description><guid>http://www.sqlservercentral.com/redirect/articles/393/</guid><pubDate>2001/09/07</pubDate><link>http://www.sqlservercentral.com/redirect/articles/393/</link></item></channel></rss>