Error Messages in Team Edition for Database Professionals

You might encounter a variety of error conditions when you use Visual Studio Team Edition for Database Professionals. For many of these errors, you can click the error in the Error List window and then press F1 for more information. This topic lists the errors for which additional information is available.

In This Section

Ambiguous column in SELECT could not be resolved

Database projects require a connection to a local instance of Microsoft SQL Server 2005 for design-time validation.

Invalid connection string. You must specify a valid connection string to build or deploy a database project.

TSD1002: The .sql file contains more than one data definition language (DDL) statement. Remove any additional statements, and retry the operation.

TSD3006: The relationship from {referencing object} cannot be resolved between the following possible identifiers: {list of options}.

TSD3007: Invalid supporting statement for {identifier}: {text}

TSD3008: The object definition cannot have a data manipulation language (DML) statement.

TSD3011: The following dependencies of {referencing object id} are missing from your database project: {list}. You will not be able to deploy the project.

TSD3012: The following dependencies are missing from your database project: {list}. Your database application might fail at runtime when {referencing object id} is executed.

TSD3017: The ALTER statement is not allowed. You must modify the object when you create it.

TSD3018: The DROP STATISTICS statement requires [schema_name.]table_name.statistics_name.

TSD3020: The database name is invalid. The substitute value '$(databasename)' should be used.

TSD3021: The following cross-server dependencies of {referencing object} could not be verified: {list}. You might not be able to deploy the project.

TSD3022: The following cross-server dependencies could not be verified: {list}. Your database application might fail at runtime when {referencing object} is executed.

TSD3023: When you create an object of this type in a database project, the objectÆs name must contain no more than two parts.

TSD3024: The following cross-database dependencies of {referencing object} could not be verified: {list}. You might not be able to deploy the project.

TSD3025: The following cross-database dependencies could not be verified: {list}. Your database application might fail at runtime when {referencing object} is executed.

TSD3032: You cannot use this statement when you create a full-text index in a database project.

TSD7025: The schema type '{0}' that the .sql file contains does not match the expected schema type '{1}', based on the name of the .sql file.

See Also

Page view tracker