Brian Kelley, noted author and database guru, offers insight on the necessity of T-SQL coding standards in this post.
"While they had naming standards for table, views, stored procedures, and other database ojects, nothing actually covered how best to implement stored procedures or what kind of T-SQL was acceptable and what needed to be justified."
Coding standards are always a difficult subject to address. I've had positive and negative experiences with them.
I've seen organizations create them in response to a coding tragedy, and I've seen organizations abandon them in response to the inflexibility of the standards.
Simply establishing a list of rules won't solve any real-world issue - at least not for long. This is especially true in the world of software where things change early and often. Coding standards need to be maintained. I believe a brief review of coding standards should be included in any project wrap-up / post-mortem process. It doesn't have to consume the meeting - it shouldn't, in fact. And it shouldn't be a philosophical debate; but rather a practical discussion of what the standards helped, hindered, or didn't address in the project.
Technorati Tags: Coding Standards T-SQL SQL Project Management