﻿<?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 Strategies, Worst Practices</title><link>http://www.sqlservercentral.com/</link><description>Content tagged Strategies, Worst Practices posted on SQLServerCentral.com</description><language>en-us</language><ttl>360</ttl><managingEditor>sjones@sqlservercentral.com (Steve Jones)</managingEditor><item><title>Worst Practice - Bad Comments</title><description>This one is pretty interesting, Andy discusses a few things he sees in comments that not only fail to add value, they end up costing extra time. There&amp;#39;s room for discussion here, but definitely a discussion worth having - comments can make you or break you, here&amp;#39;s a chance to think about what you think is important in commenting and pass that on to your development team.

</description><guid>http://www.sqlservercentral.com/articles/Miscellaneous/worstpracticebadcomments/893/</guid><pubDate>2003/01/23</pubDate><link>http://www.sqlservercentral.com/articles/Miscellaneous/worstpracticebadcomments/893/</link></item><item><title>Worst Practices - Making On-The-Fly Changes</title><description>Continuing with our worst practices series, Steve Jones looks at another administrative no-no. Making a change to your live system on the fly.

</description><guid>http://www.sqlservercentral.com/articles/Availability/worstpracticesmakingalivechange/887/</guid><pubDate>2003/01/20</pubDate><link>http://www.sqlservercentral.com/articles/Availability/worstpracticesmakingalivechange/887/</link></item><item><title>Worst Practice - Not Having An Archive Plan For Each Table</title><description>We&amp;#39;re curious to see what our readers have to say about this one! How many of us have tables accruing data that won&amp;#39;t be used and/or isn&amp;#39;t of any value? At what point do we get rid of it to free up resources?

</description><guid>http://www.sqlservercentral.com/articles/Administering/worstpracticenothavinganarchiveplanforeachtable/839/</guid><pubDate>2002/11/11</pubDate><link>http://www.sqlservercentral.com/articles/Administering/worstpracticenothavinganarchiveplanforeachtable/839/</link></item><item><title>Worst Practices - Encrypting Data</title><description>Continuing with the Worst Practices Series: Steve Jones examines why encryption in the database is a bad idea.

</description><guid>http://www.sqlservercentral.com/articles/Security/wp_encryption/527/</guid><pubDate>2002/01/08</pubDate><link>http://www.sqlservercentral.com/articles/Security/wp_encryption/527/</link></item><item><title>Worst Practices - Depending on the GUI</title><description>One of the strengths of SQL Server is its ease of management and administration over other systems. Oracle, DB2, even early versions of SQL Server required command line mastery to make many types of changes. But should you really be using the GUI for most of your tasks?

</description><guid>http://www.sqlservercentral.com/articles/Security/wp_gui/508/</guid><pubDate>2001/12/04</pubDate><link>http://www.sqlservercentral.com/articles/Security/wp_gui/508/</link></item><item><title>Worst Practices - Assigning Users Rights</title><description>Continuing with Andy Warren&amp;#39;s series on Worst Practices for a DBA, Steve Jones joins in this week with his worst practice.
</description><guid>http://www.sqlservercentral.com/articles/Security/wp_userrights/499/</guid><pubDate>2001/11/06</pubDate><link>http://www.sqlservercentral.com/articles/Security/wp_userrights/499/</link></item></channel></rss>