Transact-SQL Design Issues

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

• Subsequent changes to your database might break applications that depend on it.

• The code might not produce the expected result.

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

In general, you should not suppress a design issue because it might break your application, either now or in the future.

In This Section

Visual Studio Premium identifies the following design issues:

• SR0001: Avoid SELECT * in stored procedures, views, and table-valued functions

• SR0008: Consider using SCOPE_IDENTITY instead of @@IDENTITY

• SR0009: Avoid using types of variable length that are size 1 or 2

• SR0010: Avoid using deprecated syntax when you join tables or views

• SR0013: Output parameter (parameter) is not populated in all code paths

• SR0014: Data loss might occur when casting from {Type1} to {Type2}

Related Sections

• Analyzing Database Code to Improve Code Quality
  Describes how you can find common design, performance, and naming issues in your Transact-SQL code.

• Transact-SQL Naming Issues
  Contains links to the different types of naming 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 identify coding issues in the AdventureWorks2008 sample database.

• Create and Register Additional Rules for Analyzing Database Code
  Describes how you can create your own rules for analyzing database code to identify issues that are not found by the rules that Visual Studio Premium includes.