Ok... more often than not, I'm asked about best practices for SQL Server.  I figured I'd share my best practices bookmarks in no particular order to hopefully give you a new resource to find these.  I'd love to hear from you on what you use and what you find useful in this area.

• http://technet.microsoft.com/en-us/sqlserver/bb331794.aspx - Obviously one of my first choices.  Get the data from the horses mouth!
• http://sqlcat.com/
• http://www.sqlservercentral.com/articles/Administration/sqlserver2005bestpractices/2183/ - Registration is required to view this, but it's free.
• http://www.microsoft.com/technet/prodtechnol/sql/bestpractice/gems-top-10.mspx - Neat little nuggets for design and development in SQL Server 2005
• http://www.microsoft.com/technet/prodtechnol/sql/bestpractice/dw_perf_top10.mspx - More of a top 10 not-to-do when designing a data warehouse

On a related note... Don't forget the Microsoft Best Practices Analyzer http://www.microsoft.com/downloads/details.aspx?FamilyId=DA0531E4-E94C-4991-82FA-F0E3FBD05E63&displaylang=en.  This handy tool can review your work and point out shortcomings and compatibility issues while you're developing, rather than after you've released.

Now for my soapbox speech...  As always, rules are made to be broken.  On more than one occasion, I have had to write some code that broke one or more of these best practices.  The key is  that it was done for a specific reason, the risks were reviewed, and more than anything else, the code was tested thoroughly.