SQL Server Errors or Failures from Error: 6611 to Error: 6717

SQLServerF1

 

Error: 6611, Severity: 16, The XML data type is damaged.
Error: 6613, Severity: 16, Specified value ‘%ls’ already exists.
Error: 6621, Severity: 16, XML encoding or decoding error occurred with object name ‘%.*ls’.
Error: 6622, Severity: 16, Invalid data type for column “%ls”. The data type cannot be text, ntext, image, binary, varchar(max), nvarchar(max), varbinary(max), or xml.
Error: 6623, Severity: 16, Column ‘%ls’ contains an invalid data type. Valid data types are char, varchar, nchar, and nvarchar.
Error: 6624, Severity: 16, XML document could not be created because server memory is low. Use sp_xml_removedocument to release XML documents.

Error: 6625, Severity: 16, Could not convert the value for OPENXML column ‘%ls’ to sql_variant data type. The value is too long. Change the data type of this column to text, ntext or image.
Error: 6626, Severity: 16, Unexpected end of data stream.
Error: 6627, Severity: 16, The size of the data chunk that was requested from the stream exceeds the allowed limit.
Error: 6628, Severity: 16, %.*ls can only process untyped XML. Cast the input value to XML or to a string type.
Error: 6629, Severity: 16, The result of the column expression for column “%ls” is not compatible with the requested type “XML”. The result must be an element, text node, comment node, processing instruction, or document node.
Error: 6630, Severity: 16, Element-centric mapping must be used with OPENXML when one of the columns is of type XML.
Error: 6631, Severity: 16, The requested OpenXML document is currently in use by another thread, and cannot be used.

Error: 6632, Severity: 16, Invalid data type for the column “%ls”. CLR types cannot be used in an OpenXML WITH clause.
Error: 6633, Severity: 16, The version of MSXMLSQL.DLL that was found is older than the minimum required version. Found version “%d.%d.%d”. Require version “%d.%d.%d”.
Error: 6634, Severity: 16, OpenXML cannot be used as the target of a DML or OUTPUT INTO operation.
Error: 6700, Severity: 16, XQuery: The ‘ %ls’ operation is not supported.
Error: 6701, Severity: 16, The version of the XML index that you are trying to use is not supported anymore. Please drop and recreate the XML index.
Error: 6716, Severity: 16, XML Node ID is invalid. Re-build the database if the problem persists.
Error: 6717, Severity: 16, XQuery: The document tree is too deep. If the problem persists you must simplify the XML hierarchy.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

SQL Server Errors or Failures from Error: 4988 to Error: 5009

SQLServerF1

 

Error: 4988, Severity: 16, Cannot persist computed column ‘%.*ls’. Underlying object ‘%.*ls’ has a different owner than table ‘%.*ls’.
Error: 4989, Severity: 16, Cannot drop the ROWGUIDCOL property for column ‘%.*ls’ in table ‘%.*ls’ because the column is not the designated ROWGUIDCOL for the table.
Error: 4990, Severity: 16, Cannot alter column ‘%.*ls’ in table ‘%.*ls’ to add or remove the FILESTREAM column attribute.
Error: 4991, Severity: 16, Cannot alter NOT FOR REPLICATION attribute on column ‘%.*ls’ in table ‘%.*ls’ because this column is not an identity column.
Error: 4992, Severity: 16, Cannot use table option LARGE VALUE TYPES OUT OF ROW on a user table that does not have any of large value types varchar(max), nvarchar(max), varbinary(max), xml or large CLR type columns in it. This option can be applied to tables having large values com

Error: 4993, Severity: 16, ALTR TABLE SWITCH statement failed. The table ‘%.*ls’ has different setting for Large Value Types Out Of Row table option as compared to table ‘%.*ls’.
Error: 4994, Severity: 16, Computed column ‘%.*ls’ in table ‘%.*ls’ cannot be persisted because the column type, ‘%.*ls’, is a non-byte-ordered CLR type.
Error: 4995, Severity: 16, Vardecimal storage format cannot be enabled on table ‘%.*ls’ because database ‘%.*ls’ is a system database. Vardecimal storage format is not available in system databases.
Error: 4996, Severity: 16, Change tracking is already enabled for table ‘%.*ls’.
Error: 4997, Severity: 16, Cannot enable change tracking on table ‘%.*ls’. Change tracking requires a primary key on the table. Create a primary key on the table before enabling change tracking.
Error: 4998, Severity: 16, Change tracking is not enabled on table ‘%.*ls’.

Error: 4999, Severity: 16, Cannot enable change tracking on table ‘%.*ls’. Change tracking does not support a primary key of type timestamp on a table.
Error: 5001, Severity: 16, User must be in the master database.
Error: 5002, Severity: 16, Database ‘%.*ls’ does not exist. Verify the name in sys.databases and try the operation again.
Error: 5003, Severity: 16, Database mirroring cannot be enabled while the database has offline files.
Error: 5004, Severity: 16, To use ALTR DATABASE, the database must be in a writable state in which a checkpoint can be executed.
Error: 5005, Severity: 16, Specified recovery time of %I64d seconds is less than zero or more than the maximum of %d seconds.
Error: 5006, Severity: 16, Could not get exclusive use of %S_MSG ‘%.*ls’ to perform the requested operation.
Error: 5008, Severity: 16, This ALTR DATABASE statement is not supported. Correct the syntax and execute the statement again.
Error: 5009, Severity: 16, One or more files listed in the statement could not be found or could not be initialized.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

SQL Server Errors or Failures Error: 1087 to Error: 1124

SQLServerF1

 

Error: 1087, Severity: 15,
Must declare the table variable “%.*ls”.

Error: 1088, Severity: 15,
Cannot find the object “%.*ls” because it does not exist or you do not have permissions.

Error: 1089, Severity: 15,
The SET FMTONLY OFF statement must be the last statement in the batch.

Error: 1090, Severity: 15,
Invalid default for parameter %d.

Error: 1091, Severity: 15,
The option “%ls” is not valid for this function.

Error: 1092, Severity: 16,
In this context %d statistics name(s) cannot be specified for option ‘%ls’.

Error: 1093, Severity: 16,
%.*ls is not a valid broker name.

Error: 1094, Severity: 15,
Cannot specify a schema name as a prefix to the trigger name for database and server level triggers.

Error: 1095, Severity: 15,
%.*ls has already been specified as an event type.

Error: 1096, Severity: 15,
Default parameter values for CLR types, nvarchar(max), varbinary(max), and xml are not supported.

Error: 1097, Severity: 15,
Cannot use If UPDATE within this CREATE TRIGGER statement.

Error: 1098, Severity: 15,
The specified event type(s) is/are not valid on the specified target object.

Error: 1099, Severity: 15,
The ON clause is not valid for this statement.

Error: 1101, Severity: 17,
Could not allocate a new page for database ‘%.*ls’ because of insufficient disk space in filegroup ‘%.*ls’. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing fi

Error: 1105, Severity: 17,
Could not allocate space for object ‘%.*ls’%.*ls in database ‘%.*ls’ because the ‘%.*ls’ filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on

Error: 1119, Severity: 16,
Removing IAM page %S_PGID failed because someone else is using the object that this IAM page belongs to.

Error: 1121, Severity: 17,
Space allocator cannot allocate page in database %d.

Error: 1122, Severity: 14,
Table error: Page %S_PGID. Test (%ls) failed. Address 0x%x is not aligned.

Error: 1123, Severity: 14,
Table error: Page %S_PGID. Unexpected page type %d.

Error: 1124, Severity: 14,
Table error: Page %S_PGID. Test (%ls) failed. Slot %d, offset 0x%x is invalid.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.