Transact-SQL Performance Issues

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

• A table scan will occur when the code is executed.

In general, you might suppress a performance issue if the table contains so little data that a scan will not cause performance to drop significantly.

In This Section

Visual Studio Premium identifies the following design issues:

• SR0004: Avoid using columns that do not have indexes as test expressions in IN predicates

• SR0005: Avoid using patterns that start with “%” in LIKE predicates

• SR0006: Move a column reference to one side of a comparison operator to use a column index

• SR0007: Use ISNULL(column, default_value) on nullable columns in expressions

• SR0015: Extract deterministic function calls from WHERE predicates

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 Design Issues
  Contains links to the different types of design issues that you might find when you analyze your database code.

• Transact-SQL Naming Issues
  Contains links to the different types of naming 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.