Transact-SQL Naming Issues

When you analyze the Transact-SQL (T-SQL) code in your database project, one or more warnings might be categorized as naming issues. You should address naming issues to avoid the following situations:

• The name that you specified for an object might conflict with the name of a system object.

• The name that you specified will always need to be enclosed in escape characters (in SQL Server, '[' and ']').

• The name that you specified might confuse others who try to read and understand your code.

• The code might break if you run it with future releases of SQL Server.

In general, you might suppress a naming issue if other applications that you cannot change depend on the current name.

In This Section

Visual Studio Team System Database Edition identifies the following design issues:

• SR0011: Avoid using special characters in object names

• SR0012: Avoid using reserved words for type names

• SR0016: Avoid using sp_ as a prefix for stored procedures

Related Sections

• Improving Database Code with Static Analysis
  Describes how you can find common design, performance, and naming issues in your T-SQL code.

• Transact-SQL Design Issues
  Contains links to the different types of design issues that you might find when you analyze your database code.

• Transact-SQL Performance Issues
  Contains links to the different types of performance issues that you might find when you analyze your database code.

• Walkthrough: Analyze Transact-SQL Code for an Existing Database
  Describes how you can analyze the Northwind sample database to identify coding issues.

• Create and Register Additional Rules for Analyzing Database Code
  Describes how you can create your own rules for analyzing database code to look for issues that are not found by the built-in rules.