Information
The topic you requested is included in another documentation set. For convenience, it's displayed below. Choose Switch to see the topic in its original location.

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.

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.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

Show:
© 2014 Microsoft