﻿<?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, SQL Server 7, 2000, Miscellaneous</title><link>http://www.sqlservercentral.com/</link><description>Content tagged Database Design, SQL Server 7, 2000, Miscellaneous posted on SQLServerCentral.com</description><language>en-us</language><ttl>360</ttl><managingEditor>sjones@sqlservercentral.com (Steve Jones)</managingEditor><item><title>Worst Practices - Not Using Primary Keys and Clustered Indexes</title><description>Two weeks ago Andy started his wildly successful series on Worst Practices. This week he continues that series discussing why failing to use primary keys and clustered indexes are worst practices. Agree or disagree, read the article and join the discussion. One thing you'll have to admit, reading an article by Andy is a lot more interesting than reading Books Online!



</description><guid>http://www.sqlservercentral.com/articles/Miscellaneous/worstpracticesnotusingprimarykeysandclusteredindex/488/</guid><pubDate>2008/05/09</pubDate><link>http://www.sqlservercentral.com/articles/Miscellaneous/worstpracticesnotusingprimarykeysandclusteredindex/488/</link></item><item><title>Worst Practices - Not Using Primary Keys and Clustered Indexes</title><description>Two weeks ago Andy started his wildly successful series on Worst Practices. This week he continues that series discussing why failing to use primary keys and clustered indexes are worst practices. Agree or disagree, read the article and join the discussion. One thing you'll have to admit, reading an article by Andy is a lot more interesting than reading Books Online!



</description><guid>http://www.sqlservercentral.com/articles/Miscellaneous/worstpracticesnotusingprimarykeysandclusteredindex/488/</guid><pubDate>2008/05/09</pubDate><link>http://www.sqlservercentral.com/articles/Miscellaneous/worstpracticesnotusingprimarykeysandclusteredindex/488/</link></item><item><title>Data Dictionary from within SQL Server 2000</title><description>Mindy explores the metadata stored in SQL 2000 to show you how to produce a simple and useful data dictionary!

</description><guid>http://www.sqlservercentral.com/articles/Installation/datadictionaryfromwithinsqlserver2000/607/</guid><pubDate>2005/02/04</pubDate><link>http://www.sqlservercentral.com/articles/Installation/datadictionaryfromwithinsqlserver2000/607/</link></item><item><title>Worst Practices - Not Using Primary Keys and Clustered Indexes</title><description>Two weeks ago Andy started his wildly successful series on Worst Practices. This week he continues that series discussing why failing to use primary keys and clustered indexes are worst practices. Agree or disagree, read the article and join the discussion. One thing you'll have to admit, reading an article by Andy is a lot more interesting than reading Books Online!



</description><guid>http://www.sqlservercentral.com/articles/Miscellaneous/worstpracticesnotusingprimarykeysandclusteredindex/488/</guid><pubDate>2008/05/09</pubDate><link>http://www.sqlservercentral.com/articles/Miscellaneous/worstpracticesnotusingprimarykeysandclusteredindex/488/</link></item><item><title>An Automated Solution for Migrating Database Structures</title><description>This article by Simon Galbraith (from Red Gate software, maker of SQL Compare) discusses migrating changes from development to staging, QA, and on to production. If you&amp;#39;ve never seen the need for a schema compare tool (Steve Jones!), this is worth reading.</description><guid>http://www.sqlservercentral.com/redirect/articles/982/</guid><pubDate>2003/05/06</pubDate><link>http://www.sqlservercentral.com/redirect/articles/982/</link></item><item><title>Managing Jobs - Part 2</title><description>Jobs are pretty basic aren&amp;#39;t they? They are until you get a couple hundred, or a thousand. Andy continues talking about managing jobs by standardizing how you handle notifications and failures, and talks about an interesting idea to monitor jobs separately from SQL Agent. Worth reading!
</description><guid>http://www.sqlservercentral.com/articles/Administering/managingjobspart2/919/</guid><pubDate>2003/02/14</pubDate><link>http://www.sqlservercentral.com/articles/Administering/managingjobspart2/919/</link></item><item><title>Managing Jobs - Part 1</title><description>How many jobs do you have? 10? 100? 1000? Andy makes the point that what works to manage for a small number of jobs doesn&amp;#39;t work when that number doubles or triples (well, unless you only had 1 job to start with!). In part one of two, this article looks at ideas for using categories and naming conventions to get things under control.
</description><guid>http://www.sqlservercentral.com/articles/Administering/managingjobspart1/906/</guid><pubDate>2003/01/31</pubDate><link>http://www.sqlservercentral.com/articles/Administering/managingjobspart1/906/</link></item><item><title>Version Control for Stored Procedures</title><description>Version control for stored procedures isn&amp;#39;t always popular and certainly isn&amp;#39;t easy. Or can it be? Andy discusses a technique he used on a recent project that you might find interesting.
</description><guid>http://www.sqlservercentral.com/articles/Administering/versioncontrolforstoredprocedures/681/</guid><pubDate>2002/05/10</pubDate><link>http://www.sqlservercentral.com/articles/Administering/versioncontrolforstoredprocedures/681/</link></item><item><title>Data Dictionary from within SQL Server 2000</title><description>Mindy explores the metadata stored in SQL 2000 to show you how to produce a simple and useful data dictionary!

</description><guid>http://www.sqlservercentral.com/articles/Installation/datadictionaryfromwithinsqlserver2000/607/</guid><pubDate>2005/02/04</pubDate><link>http://www.sqlservercentral.com/articles/Installation/datadictionaryfromwithinsqlserver2000/607/</link></item><item><title>Reducing Round Trips - Part 2</title><description>Last week Andy started a discussion of the various ways you can reduce the number of round trips to the server. This week he continues by looking at a method he used recently to do client side caching of data to eliminate the round trip altogether. Gotta read it!
</description><guid>http://www.sqlservercentral.com/articles/Performance+Tuning/reducingroundtripspart2/588/</guid><pubDate>2002/02/06</pubDate><link>http://www.sqlservercentral.com/articles/Performance+Tuning/reducingroundtripspart2/588/</link></item><item><title>Understanding the Implications of ANSI SQL92 SET Options</title><description>Have you ever experienced a T-SQL query, a stored procedure, view or a trigger returning unexpected results. In this article by Raj Gill, he shows you how ANSI DEFAULTS may be to blame.

</description><guid>http://www.sqlservercentral.com/articles/Administering/understandingtheimplicationsofansisql92setoptions/482/</guid><pubDate>2001/10/18</pubDate><link>http://www.sqlservercentral.com/articles/Administering/understandingtheimplicationsofansisql92setoptions/482/</link></item></channel></rss>