http://www.sqlservercentral.com/Content tagged Best and Worst Practices, Worst Practices posted on SQLServerCentral.comen-us360sjones@sqlservercentral.com (Steve Jones)Andy Warren started his worst practice series some time ago with the intention of looking at the worst things you can do. Given that we may not always be able to implement the best practices, at least we can try to avoid doing things harm the system or decrease performance. This article continues the series and looks at an item I see mentioned in our discussion forum quite often, triggering external events. From a trigger. http://www.sqlservercentral.com/articles/Triggers/worstpracticetriggeringexternalevents/1283/2004/02/23http://www.sqlservercentral.com/articles/Triggers/worstpracticetriggeringexternalevents/1283/Adding a column is one of the simpler tasks you'll ever do as a DBA, yet danger lurks! All too often we add columns without going through some type of check list to make sure we're safe. What could adding a column break? You might be surprised! http://www.sqlservercentral.com/articles/Administering/worstpracticeaddingacolumnwithoutthinking/1288/2004/02/19http://www.sqlservercentral.com/articles/Administering/worstpracticeaddingacolumnwithoutthinking/1288/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. http://www.sqlservercentral.com/articles/Miscellaneous/worstpracticedefiningrowsthatexceedthemaxlength/1179/2003/12/08http://www.sqlservercentral.com/articles/Miscellaneous/worstpracticedefiningrowsthatexceedthemaxlength/1179/We can only guess that someone somewhere put spaces in an object name that Andy works with and gave him the idea for this worst practice. Funny as the topic may sound, we agree - why make your lifer harder? http://www.sqlservercentral.com/articles/Administering/worstpracticespacesinobjectnames/1142/2003/10/01http://www.sqlservercentral.com/articles/Administering/worstpracticespacesinobjectnames/1142/Andy returns to the Worst Practice series this week with a short article looking at how connection strings in applications affect what you see in sysprocesses. Perhaps less controversial (in our opinion) that some of the other worst practices, this is something easy to fix and definitely worth fixing! Read the article and post a comment - explore other points of view! Readers posting a comment will be entered in a drawing for a copy of the SQL Server 2000 Resource Kit. http://www.sqlservercentral.com/articles/Administering/worstpracticebadconnectionstringsandbadinfoinsyspr/802/2003/08/01http://www.sqlservercentral.com/articles/Administering/worstpracticebadconnectionstringsandbadinfoinsyspr/802/Not even worth talking about, right? Probably, but they still exist. Read about this worst practice and pass it along. http://www.sqlservercentral.com/articles/Worst+Practices/worstpractivesblankpasswords/880/2003/03/31http://www.sqlservercentral.com/articles/Worst+Practices/worstpractivesblankpasswords/880/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's room for discussion here, but definitely a discussion worth having - comments can make you or break you, here's a chance to think about what you think is important in commenting and pass that on to your development team. http://www.sqlservercentral.com/articles/Miscellaneous/worstpracticebadcomments/893/2003/01/23http://www.sqlservercentral.com/articles/Miscellaneous/worstpracticebadcomments/893/Continuing with our worst practices series, Steve Jones looks at another administrative no-no. Making a change to your live system on the fly. http://www.sqlservercentral.com/articles/Availability/worstpracticesmakingalivechange/887/2003/01/20http://www.sqlservercentral.com/articles/Availability/worstpracticesmakingalivechange/887/We're curious to see what our readers have to say about this one! How many of us have tables accruing data that won't be used and/or isn't of any value? At what point do we get rid of it to free up resources? http://www.sqlservercentral.com/articles/Administering/worstpracticenothavinganarchiveplanforeachtable/839/2002/11/11http://www.sqlservercentral.com/articles/Administering/worstpracticenothavinganarchiveplanforeachtable/839/If you've been with us for a while you know that Andy started a series last year on worst practices. As he says, maybe you can't always do best practices, but at least dont do the worst ones. Read the article and add a comment, participate! http://www.sqlservercentral.com/articles/Administering/worstpracticesortingbyordinal/811/2002/10/01http://www.sqlservercentral.com/articles/Administering/worstpracticesortingbyordinal/811/In this article by Neil Weicher, he talks about encryption of data and files for SQL Server. http://www.sqlservercentral.com/articles/Administering/securityworstpracticeneil/592/2002/01/30http://www.sqlservercentral.com/articles/Administering/securityworstpracticeneil/592/Continuing with the Worst Practices Series: Steve Jones examines why encryption in the database is a bad idea. http://www.sqlservercentral.com/articles/Security/wp_encryption/527/2002/01/08http://www.sqlservercentral.com/articles/Security/wp_encryption/527/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? http://www.sqlservercentral.com/articles/Security/wp_gui/508/2001/12/04http://www.sqlservercentral.com/articles/Security/wp_gui/508/Continuing with Andy Warren's series on Worst Practices for a DBA, Steve Jones joins in this week with his worst practice. http://www.sqlservercentral.com/articles/Security/wp_userrights/499/2001/11/06http://www.sqlservercentral.com/articles/Security/wp_userrights/499/