SQL Server Coding Guidelines

Compiled List of posts for TSQL Code Review and Best Practices

• The Curse and Blessings of Dynamic SQL
• Error Handling in SQL 2005 and Later
• Server Side Error Handling - Part 1 (Migrating from @@error to tsql try-catch)
• Server Side Error Handling - Part 2 (Errors and Error Messages)
• Server Side Error Handling - Part 3 (Why do I still see error messages from inside tsql try-block?)
• How to Share Data Between Stored Procedures
• Coding Efficient Transactions
• My stored procedure "best practices" checklist
• SQL Coding Guidelines
• Standardized SQL Server Error Handling and Centralized Logging
• SQL Server 2005 Try and Catch Exception Handling
• Avoid mixing old and new styles of error handling
• Common T-SQL mistakes
• Looking for security vulnerabilities in database code
• Server Side Error Handling - Part 1
• parameter sniffing
• Conor vs. “Does Join Order Matter?”
• Wide vs. Narrow Plans
• division by zero
• use SCOPE_IDENTITY() - @@Identity would not work in case you have a trigger enabled on the source table. Recommended to use SCOPE_IDENTITY()
• Top 10 T-SQL Code Smells
• MSDN presentation on Introducing XML in SQL Server 2005
• Proper T-SQL Stored Procedure Formatting
• The vote is in! (CHECK CONSTRAINTS vs. TRIGGERS vs. STORED PROCEDURE business logic)
• Stored Procedures are NOT evil... but they can be frustrating!
• Stored procedures are NOT bad
• Dr. Unknown, or how I learned to stop worrying and love the NULL
• Ten Common Database Design Mistakes
• Finding stored procedures containing %string%
• What should I be looking for during Code Reviews?

Happy Reading!!!