Enforcing T-SQL Coding Standards

Question

Enforcing T-SQL Coding Standards

Neal Sivley

SSCommitted

Points: 1766
More actions
January 14, 2010 at 12:49 pm

#209131

My company is looking at getting some software to enforce T-SQL coding standard, naming conversion ect, Before we started looking at all the wrong ones, I thought I would ping you guys to find out what everyone else is using and what you do and don’t like.
Thanks….

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

John Rowan SSC Guru Points: 56440 More actions · Answer 1

I've never used software for this. In fact, I was not aware that software existed that had the ability to enforce coding standards.

We have always handled coding standards enforcement by code reviews.

John Rowan

======================================================
======================================================
Forum Etiquette: How to post data/code on a forum to get the best help[/url] - by Jeff Moden

Neal Sivley SSCommitted Points: 1766 More actions · Answer 2

That is actually what I am use to doing as well, thus the post. I did hear mention of CA Erwin 4.0 but don't know much about it.

Jeff Moden SSC Guru Points: 1004318 More actions · Answer 3

Heh... there's a real easy way to enforce coding standards...

Step 1: Lockdown the server so that only authorized reviewers/DBA's can promote code.

Step 2: Publish the standards with the warning that a certain amount of pay will be docked for each standard violated in each "piece" of code.

Step 3: Do code reviews and start docking pay.

The real problem for most people isn't the enforcement of coding standards. People can write code that will meet all coding standards and still be absolute garbage and nothing that automatically checks for mere coding standards will help detect such garbage.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)