Enforce Naming Conventions

kjmcsd · June 14, 2018 3:26PM

Is there a way in SQL Source Control to check for object naming conventions and not allow check in if object is not named according to a standard?

David Atkinson · June 14, 2018 3:41PM

Have you thought about using SQL Server's built in policies to enforce this?

David Atkinson · June 14, 2018 3:33PM

Interesting idea. Can you give an example of the convention you'd like to enforce?

kjmcsd · June 14, 2018 3:37PM

Table and stored procedure names should begin with either "app" or "ssp"

kjmcsd · June 14, 2018 3:49PM

I'm looking at that right now.

AlexYates · June 14, 2018 4:12PM

Nope - but you could write a tSQLt test for it and run it as part of your build/CI processes.

kjmcsd · June 14, 2018 4:25PM

I'm finding out that policies only tell you if there are things not meeting standards. They do not enforce or prevent people from not complying with them. I think this would be a good feature to add to SQL Source Control. Adding this on the TFS side breaks SQL source control.

David Atkinson · June 14, 2018 4:34PM

Adding to Alex's suggestion, you might be able to write the tSQLt tests and have them run in a pre-commit hook, which could fail the commit should they not all pass? If this works, it would be a great blog post to share with the wider community.

AlexYates · June 14, 2018 4:49PM

Yes - that's a better idea.

Do what David said.

Enforce Naming Conventions

Best Answer

Answers

Product Learning

Community Forums

Events & Friends

Simple Talk