SQL Server
United States (English) Sign in
Home 2012 2008 R2 2008 Previous Versions Library Forums
TechNet Library
SQL Server
SQL Server 2005
Product Documentation
SQL Server 2005 Documentation
SQL Server 2005 Books Online
SQL Server Error Messages
Error Messages in Visual Database Tools
(+) operator ignored.
A blank constraint expression is not allowed. (Visual Database Tools)
A diagram with that name already exists in the database. (Visual Database Tools)
A node with the specified name already exists.
A number of rows were affected.
A pair of matching columns is required to create a relationship. (Visual Database Tools)
A primary key can't be created on column <Columnname> because it allows null values. (Visual Database Tools)
A primary key or index cannot be created on columns with a datatype of <Datatypename>. (Visual Database Tools)
A primary key or index cannot have more than <Maximum> columns. (Visual Database Tools)
A primary key or unique constraint must be defined for table <Tablename> before it can participate in a relationship. (Visual Database Tools)
A relationship cannot contain more than <Maximum> columns. (Visual Database Tools)
Adding a formula to the selected column will delete all indexes and relationships it participates in. (Visual Database Tools)
Adding a formula to the selected column will delete all relationships it participates in as a foreign key. (Visual Database Tools)
ADO Error
ALIAS name is already being used.
ALL cannot be used with CUBE or ROLLUP.
An error occurred creating the Show Differences window.
An error was encountered while generating create scripts.
An error occurred while working with Visual Database Tools.
An expression cannot be used as a parameter value.
An index already exists for table <Tablename> with the columns <Columnnames>. (Visual Database Tools)
An index can't exist on a blank column. (Visual Database Tools)
Another user modified this diagram while you were working on it. (Visual Database Tools)
Appropriate SQL cannot be generated.
Are you sure you want to delete the selected relationship from your database? (Visual Database Tools)
Are you sure that you want to permanently delete the selected database objects?
Are you sure that you want to permanently delete the specified item from the database?
Are you sure you want to permanently delete table <Tablename> from your database? (Visual Database Tools)
Are you sure you want to permanently delete the selected tables from your database? (Visual Database Tools)
Asterisk (*) may not be used in an indexed view.
At least one of these default pane view check boxes must be selected.
Bad top value.
Both sides of a relationship must have the same number of columns. (Visual Database Tools)
Cannot add folder specified.
Cannot assign alias to this field.
Cannot change the default database reference while designers are open.
Cannot convert entry to valid date/time.
Cannot convert to proper type.
Cannot create command file because the current folder contains no scripts that could be included in it.
Cannot create databases on the named server.
Cannot create databases on this server
Cannot debug stored procedures because the SQL Server database is not setup correctly or user does not have permission to execute master.sp_sdidebug.
Cannot delete rows with unknown keys.
Cannot delete these objects because they are open in designers.
Cannot delete this object because it is open in a designer.
Cannot drop the table <tablename> because it does not exist in the system catalog.
Cannot edit rows with unknown keys.
Cannot edit this cell.
Cannot filter this expression.
Cannot find document.
Cannot find Server Explorer database connection.
Cannot find the parameter grid control.
Cannot insert into this expression.
Cannot open encrypted <Viewname>.
Cannot open the .cmd file.
Cannot put expression on select list.
Cannot rename or move a file while it is open in an editor.
Cannot rename or move a folder that contains open files.
Cannot save a view/function/procedure that is self-referenced.
Cannot save a document while it is being used by TSQL debugger.
Cannot save query to a file with an extension other than '.dtq'.
Cannot save query to different connection folder.
Cannot select database objects with Unicode object names
Cannot unregister a SQL Server instance while documents are open on databases below this node.
Cannot update this expression.
Cannot use column whose data type is IMAGE or TEXT in this context.
Cannot use LONG data type in this context.
Changing a column data type results in an index that is too large. (Visual Database Tools)
Changing the column to the selected data type will delete its indexes. (Visual Database Tools)
Changing the column to the selected data type will delete its indexes and all relationships it participates in. (Visual Database Tools)
Changing the column to the selected data type will delete relationships. (Visual Database Tools)
Changing this alias will result in a duplicate output column name.
Collate clause may not be used in an indexed view.
Column cannot be updated.
<Columnname> in expression is not part of the query.
Column <Columnname> in table <Tablename> participates in index <Indexname>. Columns with a datatype of <Datatypename> cannot participate in indexes or primary keys. (Visual Database Tools)
Column <Columnname> is a computed column, and cannot contribute to foreign keys. (Visual Database Tools)
Column <Columnname> is a computed column, and cannot participate in indexes or relationships. (Visual Database Tools)
Column <Columnname> is used to enforce the full-text key on table <Tablename> and must be <Maximum> bytes or less. (Visual Database Tools)
Column <Columnname> participates in full-text indexing on table <Tablename>. After this change, the column will no longer participate in the table's full-text index. (Visual Database Tools)
Column has no name and will be deleted. (Visual Database Tools)
Column is the full-text filter for columns that participate in full-text indexing on a table. (Visual Database Tools)
Column list not supported for Make Table query.
Columns in this expression have incompatible collations.
Command file name contains invalid character(s).
Comment exceeds n bytes. (Visual Database Tools)
Connection failure. (Visual Database Tools)
Conversion between the specified data types is not supported on the connected database server.
Could not automatically discover any SQL Server instances.
Could not create the specified file in project.
Data has changed since the Results pane was last retrieved.
Data source alias is read only.
Data source base name is read only.
Data Source Locator is missing.
Data type error in expression.
Data type mismatch - no conversion possible.
Data type mismatch - use the CONVERT function.
Database Designer Error. (Visual Database Tools)
Database object specified already exists. Choose a unique name.
Database Project files must have .dbp file extension.
Database Server Version Run-time Error.
Default Value property cannot be set on column <Columnname> because it is a computed column. (Visual Database Tools)
DELETE statement conflicted with COLUMN REFERENCE constraint.
Deleting the selected columns will also delete relationships. (Visual Database Tools)
Differences were detected in the specified object while you were working on it.
Do you want to prolong your work with the Results pane?
Do you want to save changes in this diagram? (Visual Database Tools)
Do you want to save changes in this table? (Visual Database Tools)
Do you want to suppress further error messages telling you why records can't be pasted?
Dragged object has invalid database object information.
Editing this default will permanently unbind the named default. (Visual Database Tools)
Edits not allowed. Having clause not allowed in an indexed view.
Enter an integer between 0 and 100.
Enter an expression in the Column cell first.
Enter a source control project name.
Enter a source control database location.
Entry must match an item in the list.
Error after predicate near <Stringname>.
Error after function <Functionname>.
Error before EXISTS clause.
Error before EXISTS clause: <Stringname> not recognized.
Error before FROM clause.
Error creating the specified directory.
Error following UNION operator.
Error in column list.
Error in column list: <Stringname> not recognized.
Error in destination table specification.
Error in FROM clause near <Stringname>.
Error in GROUP BY clause.
Error in GROUP BY clause near <Stringname>.
Error in HAVING clause.
Error in HAVING clause near <Stringname>.
Error in INSERT statement.
Error in INSERT statement: <Stringname> not recognized.
Error in join expression.
Error in join expression: Stringname not recognized.
Error in list of function arguments: <Stringname> not recognized.
Error in list of values: <Stringname> not recognized.
Error in list of values.
Error in list of values in IN clause.
Error in list of values in IN clause: <Stringname> not recognized.
Error in values list in INSERT INTO clause: <Stringname> not recognized.
Error in ON clause near < Stringname>.
Error in optional FROM clause.
Error in ORDER BY clause.
Error in ORDER BY clause near <Stringname>.
Error in SELECT clause: alias <Aliasname> not recognized.
Error in SELECT clause: alias not recognized.
Error in SELECT clause: expression near <Stringname>.
Error in set list in UPDATE clause.
Error in table name or view name in DELETE clause.
Error in table name or view name in DELETE clause: <Stringname> not recognized.
Error in table name or view name in INSERT clause.
Error in table name or view name in INSERT clause: <Stringname> not recognized.
Error in table name or view name in UPDATE clause.
Error in text following query statement: <Stringname>.
Error in values list in INSERT INTO clause.
Error in WHERE clause near <Stringname>.
Error loading table. (Visual Database Tools)
Error moving file specified.
Error moving folder specified.
Error pasting file into project
Error reloading the project.
Error validating constraint. (Visual Database Tools)
Error validating the default for column. (Visual Database Tools)
Error validating the formula for column. (Visual Database Tools)
Failed to allocate connection.
Failed to design object.
Failed to enumerate objects.
Failed to load source for stored procedure.
Failed to load the function.
Failed to load the trigger.
Failed to open object.
<Featurename> support not available in this server version.
Files and folders cannot be named '.' or '..', nor can they contain any of the following characters:
File specified cannot be found.
File specified not found.
Folder specified already exists.
Function argument count error.
Generating create scripts is not supported by the database reference.
Identity seed must be a number containing <Maximum> digits or less. (Visual Database Tools)
If you change a file name extension, the file may become unusable.
If you save the view encrypted, you will no longer be able to alter the view definition.
Ignoring illegal use of ALL.
Ignoring ODBC syntax.
Illegal use of expression list.
Illegal sequence use.
Illegal use of collation clause.
Incomplete column list.
Incomplete parameters list.
Incomplete parameters or column list.
Incomplete SET clause.
Incomplete VALUES list.
Index already exists.
Index <Indexname> is used to enforce the full-text key on table <Tablename> and must be <Maximum> bytes or less. (Visual Database Tools)
Index <Indexname> is used to enforce the full-text key on table <Tablename> and must be single-column. (Visual Database Tools)
Index <Indexname> is used to enforce the full-text key on table <Tablename> and must be unique. (Visual Database Tools)
Index <Indexname> is used to enforce the full-text key on table <Tablename> and must not be null. (Visual Database Tools)
Index must have at least one column.
Indexed View must contain a clustered index.
Internal Error. (Visual Database Tools)
Internal Error. An error occurred trying to create the database but error information is not available.
Invalid Datatype.
Invalid entries must be resolved before you can exit this pane.
Invalid escape character. (Visual Database Tools)
Invalid fill factor; enter an integer between 0 and 100.
Invalid identifier <Stringname>.
Invalid name. You must provide a name for this object. (Visual Database Tools)
Invalid prefix or suffix characters. (Visual Database Tools)
Invalid or missing expression.
Invalid or missing expression near <Stringname>.
Invalid row index: Goto failed.
Invalid text or symbol.
Invalid value.
Invalid view name.
IS operator can only be used with NULL or NOT NULL.
Item specified does not exist in the project directory.
Item specified is currently open in an editor.
It is only possible to connect to SQL Server Desktop Engine databases and Microsoft Access databases with this version of Visual Studio.
Illegal use of outer join operator.
Link server object cannot be used as a destination with this query type.
Literal of the correct data type required.
Missing escape character in LIKE predicate.
Missing FROM clause.
Missing FROM clause near <Stringname>.
Missing FROM keyword.
Missing FROM keyword near <Stringname>.
Missing INTO keyword.
Missing INTO keyword near <Stringname>.
Missing or incomplete SELECT clause.
Missing pattern in LIKE predicate.
Missing SET keyword.
Missing subquery.
Missing subquery correlation name.
Missing subquery or the operator you entered requires parenthesis.
Must enter either TRUE or FALSE.
Name entered is not valid.
Name is greater than 30 characters.
Name is too long.
Need alias for this field.
No rows were deleted.
No rows were updated.
NOT cannot be used in a column cell.
Object name cannot begin with #. (Visual Database Tools)
Object with name already exists in the database. (Visual Database Tools)
ODBC driver returned an invalid ODBC version and needs to be updated.
ODBC error: <Error>. (Visual Database Tools)
One or more selected tables are already on the diagram. (Visual Database Tools)
Only one clustered index can be created on table <Tablename>. (Visual Database Tools)
Only one ROWGUID column is allowed per table. (Visual Database Tools)
OpenRowset cannot be used as a destination with this query type.
ORDER BY not supported for CREATE TABLE query.
Out of memory executing database object.
Outer join column may not be used with an IN predicate or subquery.
Path name too long.
Poorly formed cast function.
Poorly formed comment.
Primary key or index cannot be created on a column with no name. (Visual Database Tools)
Primary key or index cannot be created on column <Columnname> because its data type is <Datatypename>. (Visual Database Tools)
Problem running SQL.
Project file is corrupted.
Property cannot be modified. (Visual Database Tools)
Query Designer cannot open this query file.
Query Designer Error.
Query Designer requires a database reference.
Query Designer supports no more than 1 table for this type of query.
Query file is corrupted.
Query has executed successfully.
Query or View already exists. Do you want to overwrite it?
Query or View has been modified. Save changes before closing?
Relationship <Relationshipname> was modified or deleted since the diagram was loaded. (Visual Database Tools)
Removing the formula from the selected column leaves it with data type that is disallowed in indexes and relationships. (Visual Database Tools)
Row limit value should be between <Minimum> and <Maximum>.
Rows pasted.
Runtime Error: Arithmetic overflow error converting expression to data type int.
Save As for a database project must not change the directory.
Select both primary key table and foreign key table before selecting any field for the relationship. (Visual Database Tools)
Setting for Length must be from <Minimum> to <Maximum>. (Visual Database Tools)
Setting for Precision must be from <Minimum> to <Maximum>. (Visual Database Tools)
Setting for Scale must be from <Minimum> to <Maximum>. (Visual Database Tools)
Server Explorer is not working.
Some of the selected database objects will not be deleted because they are open in designers.
Some program files are not properly registered on your machine.
Specify a name.
Specify the command file name.
SQL Execution Error.
SQL statement could not be parsed.
SQL text cannot be represented in the grid pane and diagram pane.
SQL Verify failed.
Syntax error in table reference.
Syntax error in table reference: <Stringname> not recognized.
Table <Tablename> already exists. (Visual Database Tools)
Table <Tablename> has no columns. (Visual Database Tools)
Table <Tablename> is marked for deletion and was not added to the diagram. (Visual Database Tools)
Table <Tablename> no longer exists in the database. (Visual Database Tools)
Table <Tablename> is set to read only, user doesn't have enough rights on this table.
Table is not in the query definition.
Table name cannot include the double-quote character.
The alias name is too long.
The Allow Nulls property can't be set on a column that is part of the primary key. (Visual Database Tools)
The Allow Nulls property can't be set on column <Columnname> because it is an identity column. (Visual Database Tools)
The collation properties of columns <Columnname> and <Columnname> do not match. (Visual Database Tools)
The columns in table <Tablename> do not match an existing primary key or UNIQUE constraint. (Visual Database Tools)
The columns in table <Tablename> do not match an existing enabled primary key or UNIQUE constraint. (Visual Database Tools)
The command file name has already been used.
The connection failed.
The database cannot create objects of this type.
The database name is not specified.
The database object no longer exists.
The database row you are modifying no longer exists in the database.
The database server name is not specified.
The datatype of column <Columnname> in the <Tablename> table can't be changed because it participates in index <Indexname>. (Visual Database Tools)
The Default Value property can't be set on column <Columnname> because it is an identity column. (Visual Database Tools)
The document cannot be found in the database connection.
The existing relationship must have at least one pair of related columns. (Visual Database Tools)
The following datatype or size property of <Tablename>.<Columnname> doesn't match <Tablename>.<Columnname>. (Visual Database Tools)
The following error was encountered while changing the collation: <Error>. (Visual Database Tools)
The following schema-bound objects will be modified. (Visual Database Tools)
The identity increment must be a number containing <Maximum> digits or less. (Visual Database Tools)
The Identity property can't be set on column <Columnname> because it allows null values. (Visual Database Tools)
The Identity property can't be set on column <Columnname> because it has a default value. (Visual Database Tools)
The index is used to enforce the full-text key for this table. Deleting this index will disable full-text indexing for the table. Do you want to proceed? (Visual Database Tools)
The name is too long. (Visual Database Tools)
The name specified is invalid because it is empty, contains invalid characters, or contains more than 128 characters.
The new relationship must have at least one pair of related columns. (Visual Database Tools)
The NOT keyword may not be used in a column cell.
The number of selected columns exceeds the number of columns in the target table. (Visual Database Tools)
The primary key or UNIQUE constraint cannot be changed until its existing relationships are deleted. (Visual Database Tools)
The primary key or Unique constraint cannot be changed while relationships to the existing primary key or Unique constraint are enforced. (Visual Database Tools)
The project file uses an old format.
The query cannot be executed because some files are missing or not registered.
The query cannot be run until it has been designed.
The Query Designer does not support the critical ODBC APIs.
The Query Designer does not support the current ODBC API.
The Results pane has been cleared to conserve server resources.
The specified database reference node already exists.
The specified item is open in an editor.
The specified object already exists.
The specified OR group number is already in use.
The specified syntax cannot be used in this query type.
The SQL Server does not meet minimum requirements of version 6.5 service pack 3. (Visual Database Tools)
The SQL syntax has been verified against the data source.
The stored procedure or scalar function <Name> cannot be specified as a FROM clause reference or as a target for an UPDATE, INSERT or DELETE statement.
The table being loaded into memory has a user-defined data type that is not recognized. (Visual Database Tools)
The table must have at least one column that is not computed. (Visual Database Tools)
The table-valued function used as target is not an in-line function.
The total size of an index or primary key cannot exceed 900 bytes.
The valid default length range for SQL Server data types char, varchar, binary and varbinary is 1-8000.
The valid default length range for SQL Server data types nchar and nvarchar is 1-4000.
The valid range for 'Commit time-out' is 1-65535.
The valid range for 'Limit SQL results sent to Output window' is 1-65535.
The valid range for 'SQL login time-out' is 1-65535.
The valid range for 'SQL query time-out' is 1-65535.
The value for the extended property is too long. (Visual Database Tools)
The value you entered is not consistent with the data type or length of the column.
There are no columns selected. Please select one or more columns and re-run the query
There are not enough columns in the subquery select list.
There are not enough columns to match the value list.
There are too many values from the sub-query select list.
There is no unique table in this query.
This cell contains the text string "<NULL>" which may not be processed correctly.
This command is not supported by this provider.
This database version is not supported for designing database diagrams, tables, or views. (Visual Database Tools)
This designer does not graphically support the specified SQL construct.
This is the default database reference.
This operator cannot be used with columns with data type "uniqueidentifier".
This SQL statement type cannot be used in a view.
To use this feature, you must install SQL Server 2000 Client Tools.
Too many characters for field width.
Too many or too few parameters specified.
Unable to connect to a database specified in the solution.
Unable to create the command file.
Unable to execute create script because it does not begin with CREATE. (Visual Database Tools)
Unable to execute create script because it does not begin with CREATE or ALTER. (Visual Database Tools)
Unable to execute create script because it does not begin with CREATE or CREATE OR REPLACE. (Visual Database Tools)
Unable to execute the create script; the table name is invalid or missing. (Visual Database Tools)
Unable to locate data source.
Unable to parse expression.
Unable to parse query text.
Unable to parse statement.
Unable to read object text; the text is encrypted. (Visual Database Tools)
Unable to save project file specified.
Unable to save; the object name is invalid or missing. (Visual Database Tools)
Undo Checkout succeeded. Compile failed.
Unexpected function type.
Unexpected internal failure while adding create scripts.
Unexpected object type. (Visual Database Tools)
Unknown column.
Unknown conversion specification.
Unknown Error
Unquoted alias contains white space.
Use of CONVERT function might be unnecessary.
Use of GROUP BY function in WHERE clause not allowed.
Using source control for stored procedures exposes your database to security risks.
Values for property must lie within the range x to y. (Visual Database Tools)
Values for <Propertyname> must lie within the range <Minimum> to <Maximum>. (Visual Database Tools)
View already exists in the database.
View definition includes no output columns or no items in the FROM clause.
View has indexes. If you remove schema binding, the indexes will be dropped.
View name cannot begin with #.
Warning: It is likely that the modification will result in a view that cannot be indexed.
Warning: It is likely that the view definition will result in a view that cannot be indexed.
WITH TIES clause requires an ORDER BY clause.
You are about to delete a row or rows.
You are about to paste n rows.
You are not logged in as the database owner or as a user that is a member of the db_owner role. You will not be able to save changes to tables that you do not own. (Visual Database Tools)
You cannot change the object type in a script.
You cannot create a view which is self-referenced.
You entered <Number> characters for <Propertyname>. The maximum number of characters allowed is <Maximum>. (Visual Database Tools)
You entered x characters for a property; the maximum allowed is y. (Visual Database Tools)
You have made changes to your batch file.
You have modified the text of the stored procedure in the editor only.
You have specified SQL Server authentication, but you have not supplied a user id.
You might not have permission to perform this operation, or the object <Objectname> might no longer exist in the database.
You must save the object first.
You must select a database reference or connection.
Your database project has a database reference that uses an OLEDB provider.
Your diagram will be updated with the following changes to match the database before the following tables can be loaded. (Visual Database Tools)
Your entry cannot be converted to a valid date time value.
Your Logon does not have CREATE TABLE permission; you might not be able to make certain edits that require this permission. (Visual Database Tools)
Your table will be updated with the following changes to match the database. (Visual Database Tools)
Expand Minimize
1 out of 14 rated this helpful - Rate this topic

Cannot debug stored procedures because the SQL Server database is not setup correctly or user does not have permission to execute master.sp_sdidebug.

SQL Server 2005

When debugging stored procedures, the debug process fails if a SQL Server login user does not have Execute permission granted to the extended stored procedure sp_sdidebug in the master database.

To debug stored procedures, you need to have appropriate user permissions to execute the extended stored procedure sp_sdidebug. The default access is for system administrators only.

This error can also occur if the SQL Server database debugging software (both server-side and client-side) is not setup correctly.

  1. Ask the database administrator for permissions to run the extended stored procedure sp_sdidebug.

Did you find this helpful?
(1500 characters remaining)

Community Additions

ADD
© 2013 Microsoft
|
Site Feedback
© 2013 Microsoft. All rights reserved.