http://www.sqlservercentral.com/Content tagged Miscellaneous, Worst Practices posted on SQLServerCentral.comen-us360sjones@sqlservercentral.com (Steve Jones)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/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/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/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/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/