HomeSQL ServerSQL Server Error Messages 13001 to 14000

SQL Server Error Messages 13001 to 14000

In this post, we’ll list out the SQL Server Error Messages from the error codes 13001 to 14000 and references to the detailed post to know more about the errors and how to fix them when using SQL Server as database in your application.

SQL Server Error Messages 13001 to 14000

ErrorCodeSeverityErrorMessage
1300116file name
1300216audit
1300316audit specification
1300416audit name
1300516server role
1300616server principal
130080receive
130100read
130120a USE database statement
130130a procedure, function or trigger
130140indexed views and/or indexes on computed columns and/or filtered indexes and/or query notifications and/or XML data type methods and/or spatial index operations
130150spatial index operations
130160an INTO clause
130190a SELECT INTO statement
130200option
130210offset option
130220statistics option
130240function name
130250varbinary (128) NOT NULL
130260parameter
130270convert specification
130280index
130290table
130300database
130310procedure
130320trigger
130330view
130340default
130350rule
130360system table
130370unknown type
130380SET option
130390column
130400type
130410character string
130420integer
130430identifier
130440number
130450indexes
130470object
130490built-in function name
130500aggregate function
130510XML INDEX
130520CLR type
130530xml schema collection
130540EXTENDED INDEX
130550SPATIAL INDEX
130560spatial
130570a planguide batch
130580geometry or geography
130590conversation priority
130600tablegroup
130760an assignment
130770a cursor declaration
130780replication filter
130790variable assignment
130800statistics
130810file
130820filegroup
130830server
130840write
130850function
130860database collation
130870drop
130880alter
130890message type
130900contract
130920service
130930queue
130940table valued function
130950event notification
130960synonym
130970lock
130980thread
130990communication buffer
131000Common Language Runtime critical section
131010partition scheme
1310210DETACH
131030protocol version
131050create
131060route
131070remote service binding
131080Initiator
131090Target
131100host synchronization object
131110generic waitable object
131120application role
131130schema
131140user
131150login
131160certificate
131170role
131180find
131190endpoint
131200sql:variable
131210sql:column
131220XML namespace
131230assembly
131240fulltext catalog
1312516execute as
1312616symmetric key
1312716principal
1312816security descriptor
1312916hypothetical index
1313016nonclustered index
1313116credential
131320transfer
131330Cumulative wait time (ms) per second
131340Waits started per second
131350Waits in progress
131360Average wait time (ms)
131370Cumulative execution time (ms) per second
131380Execs started per second
131390Execs in progress
131400Average execution time (ms)
1314116asymmetric key
131420an INSERT SELECT statement
1314316partition function
1314416partition scheme
1314516encryption
1314616signature
1314716password
1314816rename
1314916end dialog
1315016END CONVERSATION WITH ERROR
1315116MOVE CONVERSATION
1315216receive sequenced message
1315316receive end conversation
1315416receive end conversation with error
1315516receive broker error
1315616receive message acknowledgement
1315716terminate conversation
1315816broker error
1315916countersignature
1316016BEGIN CONVERSATION TIMER
1316116fire conversation timer
1316216END CONVERSATION WITH CLEANUP
1316316BEGIN DIALOG CONVERSATION
1316416SEND
1316516conversation
1316616conversation group
1316716system
1316816Service Broker
1316916Database Mirroring
131700table or indexed view
1317116conversation handle
1317216GET CONVERSATION GROUP
1317316master key
1317416another assembly with same SQL name is already present in the current database
1317516version, culture or public key mismatch
131760component
1317716IL compilation
1317816Inproc data access
1317916DDL operations
1318016execution cache cleanup
1318116unspecified operation
1318216dialog
1318310The certificate’s private key cannot be found
1318410The certificate’s private key size is incompatible with the crypto provider
1318510The certificate’s public key size is incompatible with the crypto provider
1318610The certificate’s private key size is incompatible with the encrypted key exchange key
1318710The certificate’s public key size is incompatible with the security header’s signature
1318810The certificate’s private key is password protected
1318910The key exchange key has an invalid size after being decrypted with the certificate private key
1319010The database principal used to lookup the cert is invalid
1319110The database principal has no mapping to a server principal
1319210The certificate is disabled for BEGIN DIALOG
1319316encryption algorithm
1319416authentication protocol
1319510Certificate not found
1319610Certificate not yet valid
1319710Certificate expired
1319810Certificate is larger than maximum allowed size
1319910message timestamp
1320210TO BROKER INSTANCE
1320310TO SERVICE
1320410FROM BROKER INSTANCE
1320510FROM SERVICE
1320610SERVICE CONTRACT
1320710MESSAGE TYPE
1320810MESSAGE INTEGRITY CHECK
1320910KEY SALT
1321010SESSION KEY
1321110KEY EXCHANGE KEY
1321210SOURCE CERTIFICATE ISSUER NAME
1321310SOURCE CERTIFICATE SERIAL NUMBER
1321410DESTINATION CERTIFICATE ISSUER NAME
1321510DESTINATION CERTIFICATE SERIAL NUMBER
1321610SECURITY HEADER SIGNATURE
1321710MESSAGE BODY
1321810STATEMENT
1321910clustered index
1322010primary xml index
1322110manual failover
1322210automatic failover
1322310failover from partner
1322410role synchronization
1322510FORCE_SERVICE_ALLOW_DATA_LOSS
1322610add
1322710to
1322810from
1322910enable
1323010disable
1323110remap
1323210INSERT
1323310UPDATE
1323410DELETE
1323510WHEN MATCHED
1323610WHEN NOT MATCHED
1323710WHEN NOT MATCHED BY SOURCE
1323810TOP or OFFSET
1323910GROUP BY
1324010HAVING
1324110ORDER BY
1324310OUTPUT INTO
1324410SELECT
1324510WHERE
1324610unexpected
1324710The crypto API has detected bad data while trying to perform a decryption operation
1324810OUTPUT
1324910Temporary tables
1325010Labels
1325110availability group
1325210type table
1325410event
1325510target
1325610event action
1325710event session
1325810event package
1325910event object
1326010event predicate comparator
1326110event attribute or predicate source
1326210customizable attribute
1326310event predicate
1326410predicate source
1326510event attribute
1326610partitioned
1326710not partitioned
1326810resource pool
1326910workload group
1327010resource governor
1327110move
1327210UPDATETEXT
1327310WRITETEXT
1327410torn page (expected signature: 0x%08x; actual signature: 0x%08x)
1327510incorrect checksum (expected: 0x%08x; actual: 0x%08x)
1327610invalid protection option
1327710invalid encryption key
1327810unable to decrypt page
1327910decryption failure (expected: 0x%08x; actual: 0x%08x)
1328010unable to decrypt page due to missing DEK
1328110CREATION_DISPOSITION
1328210PROVIDER_KEY_NAME
1328310key source
1328410ENCRYPTION BY
1328510public key
1328610private key
1328710cryptographic provider
1328810cryptographic provider DLL path
1328910cryptographic provider friendly name
1329010version
1329110guid
1329210create credential for
1329310cryptographic provider key name
1329410key persistence
1329510cryptographic provider key thumbprint length
1329610cryptographic provider key blob length
1329716encryption algorithm tag
1329816name
1329916thumbprint
1330116IV(Initialization Vector) length
1330216bit length
1330316constraint
1330416database encryption key
1330510QUERY_STORE
1330610DESIRED_STATE’ or ‘OPERATION_MODE
1330710MAX_STORAGE_SIZE_MB
1330810FLUSH_INTERVAL_SECONDS’ or ‘DATA_FLUSH_INTERVAL_SECONDS
1330910QUERY_STORE CLEANUP_POLICY
1331010STALE_QUERY_THRESHOLD_DAYS
1331110column master key
1331210column encryption key
1331310key store provider name
1331410FILESTREAM
1331510ROWGUID
1331610FOR XML
1331710FOR JSON
1331810encrypted value
1331910key path
1332010BLOCK
1332110FILTER
1332210INTERVAL_LENGTH_MINUTES
1332310MAX_PLANS_PER_QUERY
1332410QUERY_CAPTURE_MODE
1332510SIZE_BASED_CLEANUP_MODE
1332610external resource pool
1332710external library
1332810QUERY_TUNING_MODE
1332910QDS server name
1333010WAIT_STATS_CAPTURE_MODE
1333110external language
1333210maximum
1333310total
1337110STATISTICS_INCREMENTAL
1337210this operation cannot be performed inside a user transaction.
1337316Anchor record
1337416Page dictionary
1337516Compression information structure
1337610Fulltext Query String
1337710Fulltext Query Language
1337810Fulltext Query Max Keys
1337910fulltext stoplist
1338010Success – Consult EKM Provider for details
1338110Failure – Consult EKM Provider for details
1338210Insufficient Buffer – Consult EKM Provider for details
1338310Not Supported – Consult EKM Provider for details
1338410Object Not Found – Consult EKM Provider for details
1338510Authentication Failure – Consult EKM Provider for details
1338610Invalid Argument – Consult EKM Provider for details
1338710Provider Error – No explanation is available, consult EKM Provider for details
1338810Key Flags
1338910Key Name
1339010Key Type
1339110Location:
1339210Location relative to the specified target node:
1339310search property list
1339410MERGE
1339510PAD_INDEX
1339610FILLFACTOR
1339710SORT_IN_TEMPDB
1339810IGNORE_DUP_KEY
1339910STATISTICS_NORECOMPUTE
1340010Extended stored procedure API will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it.
1340210The ability to INSERT NULL values into TIMESTAMP columns will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it. Use DEFAULT instead.
1340310The ability to use string literals as column aliases will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it. Use AS clause instead.
1340410The ability to use ‘#’ and ‘##’ as the name of temporary tables and stored procedures will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it.
1340510The ability to use ‘@’ and names that start with ‘@@’ as Transact-SQL identifiers will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it.
1340610The ability to use the DEFAULT keyword as a default value will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it.
1340710FASTFIRSTROW hint will be removed in the next version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it. Use OPTION (FAST n) instead.
1340810%ls will be removed in the next version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it.
1340910Collation ‘%ls’ will be removed in a future version of SQL Server. Avoid using this collation in new development work, and plan to modify applications that currently use it.
1341010Creating credentials using mismatched password for sp_control_dbmasterkey_password will be removed in a future version of SQL Server. Avoid using this stored procedure with passwords that do not match the existing database master key’s encryption password, and plan to modify applications that currently use it.
1350116Temporal generated always column ‘%.*ls’ has invalid data type.
1350216System-versioned table cannot have more than one ‘GENERATED ALWAYS AS ROW START’ column.
1350316System-versioned table cannot have more than one ‘GENERATED ALWAYS AS ROW END’ column.
1350416Temporal ‘GENERATED ALWAYS AS ROW START’ column definition missing.
1350516Temporal ‘GENERATED ALWAYS AS ROW END’ column definition missing.
1350616System-versioned table SYSTEM_TIME period definition start column name not matching ‘GENERATED ALWAYS AS ROW START’ column name.
1350716System-versioned table SYSTEM_TIME period definition end column name not matching ‘GENERATED ALWAYS AS ROW END’ column name.
1350816System-versioned table cannot have more than one SYSTEM_TIME period definition.
1350916Cannot create generated always column when SYSTEM_TIME period is not defined.
1351016Cannot set SYSTEM_VERSIONING to ON when SYSTEM_TIME period is not defined.
1351116Specified object ‘%.*ls’ cannot be used as history table.
1351216You cannot specify SYSTEM_VERSIONING clause more than once.
1351316SYSTEM_TIME period columns cannot have different datatype precision.
1351416History table ‘%.*ls’ is already in use.
1351516Setting SYSTEM_VERSIONING to ON failed because history table ‘%.*ls’ has custom unique keys defined. Consider dropping all unique keys and trying again.
1351616Setting SYSTEM_VERSIONING to ON failed because history table ‘%.*ls’ has foreign keys defined. Consider dropping all foreign keys and trying again.
1351716Setting SYSTEM_VERSIONING to ON failed because history table ‘%.*ls’ has table or column constraints defined. Consider dropping all table and column constraints and trying again.
1351816Setting SYSTEM_VERSIONING to ON failed because history table ‘%.*ls’ has IDENTITY column specification. Consider dropping all IDENTITY column specifications and trying again.
1351916Setting SYSTEM_VERSIONING to ON failed because history table ‘%.*ls’ has computed column specification. Consider dropping all computed column specifications and trying again.
1352016Setting SYSTEM_VERSIONING to ON failed because history table ‘%.*ls’ is not available or it is placed on a read-only file group.
1352116Setting SYSTEM_VERSIONING to ON failed because history table ‘%.*ls’ is configured for change data capture. Consider dropping this configuration and trying again.
1352216Setting SYSTEM_VERSIONING to ON failed because history table ‘%.*ls’ has triggers defined. Consider dropping all triggers and trying again.
1352316Setting SYSTEM_VERSIONING to ON failed because table ‘%.*ls’ has %d columns and table ‘%.*ls’ has %d columns.
1352416Setting SYSTEM_VERSIONING to ON failed because column ‘%.*ls’ at ordinal %d in history table ‘%.*ls’ has a different name than the column ‘%.*ls’ at the same ordinal in table ‘%.*ls’.
1352516Setting SYSTEM_VERSIONING to ON failed because column ‘%.*ls’ has data type %s in history table ‘%.*ls’ which is different from corresponding column type %s in table ‘%.*ls’.
1352616Setting SYSTEM_VERSIONING to ON failed because column ‘%.*ls’ does not have the same collation in tables ‘%.*ls’ and ‘%.*ls’.
1352716Setting SYSTEM_VERSIONING to ON failed because column ‘%.*ls’ does not have the same CLR type in tables ‘%.*ls’ and ‘%.*ls’.
1352816Setting SYSTEM_VERSIONING to ON failed because column ‘%.*ls’ does not have the same ANSI trimming semantics in tables ‘%.*ls’ and ‘%.*ls’.
1352916Setting SYSTEM_VERSIONING to ON failed because column ‘%.*ls’ does not have the same XML Schema Collection in tables ‘%.*ls’ and ‘%.*ls’.
1353016Setting SYSTEM_VERSIONING to ON failed because system column ‘%.*ls’ in history table ‘%.*ls’ corresponds to a period column in table ‘%.*ls’ and cannot be nullable.
1353116Setting SYSTEM_VERSIONING to ON failed because column ‘%.*ls’ does not have the same nullability attribute in tables ‘%.*ls’ and ‘%.*ls’.
1353216Setting SYSTEM_VERSIONING to ON failed because system-versioned tables cannot have FILESTREAM columns.
1353316Setting SYSTEM_VERSIONING to ON failed because column ‘%.*ls’ does not have the same sparse storage attribute in tables ‘%.*ls’ and ‘%.*ls’.
1353416Setting SYSTEM_VERSIONING to ON failed because column ‘%.*ls’ does not have the same column set property in tables ‘%.*ls’ and ‘%.*ls’.
1353516Data modification failed on system-versioned table ‘%.*ls’ because transaction time was earlier than period start time for affected records.
1353616Cannot insert an explicit value into a GENERATED ALWAYS column in table ‘%.*ls’. Use INSERT with a column list to exclude the GENERATED ALWAYS column, or insert a DEFAULT into GENERATED ALWAYS column.
1353716Cannot update GENERATED ALWAYS columns in table ‘%.*ls’.
1353816You do not have the required permissions to complete the operation.
1353916Setting SYSTEM_VERSIONING to ON failed because history table ‘%.*ls’ is not specified in two-part name format.
1354016Setting SYSTEM_VERSIONING to ON failed because table ‘%.*ls’ contains invalid records with end of period set before start.
1354116Setting SYSTEM_VERSIONING to ON failed because history table ‘%.*ls’ contains invalid records with end of period set before start.
1354216ADD PERIOD FOR SYSTEM_TIME on table ‘%.*ls’ failed because there are open records with start of period set to a value in the future.
1354316Setting SYSTEM_VERSIONING to ON failed because history table ‘%.*ls’ contains invalid records with end of period set to a value in the future.
1354416Temporal FOR SYSTEM_TIME clause can only be used with system-versioned tables. ‘%.*ls’ is not a system-versioned table.
1354516Truncate failed on table ‘%.*ls’ because it is not a supported operation on system-versioned tables.
1354616Switching out partition failed on table ‘%.*ls’ because it is not a supported operation on system-versioned tables. Consider setting SYSTEM_VERSIONING to OFF and trying again.
1354716Switching in partition failed on history table ‘%.*ls’ because it is not a supported operation on system-versioned tables. Consider setting SYSTEM_VERSIONING to OFF and trying again.
1354816Cannot alter column ‘%.*ls’ on table ‘%.*ls’ because it is not a supported operation on system-versioned temporal tables.
1354916Setting FILESTREAM ON failed on table ‘%.*ls’ because it is not a supported operation on system-versioned temporal tables.
1355016Add column operation failed on table ‘%.*ls’ because it is not a supported operation on system-versioned temporal tables.
1355116Drop column operation failed on table ‘%.*ls’ because it is not a supported operation on system-versioned temporal tables.
1355216Drop table operation failed on table ‘%.*ls’ because it is not a supported operation on system-versioned temporal tables.
1355316System versioned temporal table ‘%.*ls’ must have primary key defined.
1355416Memory-optimized table ‘%.*ls’ cannot contain system-time PERIOD.
1355516System versioned temporal table ‘%.*ls’ cannot have FILESTREAM columns.
1355616Table ‘%.*ls’ is a FileTable. System versioning cannot be used on FileTables.
1355716Cannot drop PRIMARY KEY constraint from a system-versioned temporal table ‘%.*ls’.
1355816Cannot add PRIMARY KEY constraint to a temporal history table ‘%.*ls’.
1355916Cannot insert rows in a temporal history table ‘%.*ls’.
1356016Cannot delete rows from a temporal history table ‘%.*ls’.
1356116Cannot update rows in a temporal history table ‘%.*ls’.
1356216Cannot perform MERGE operation on temporal history table ‘%.*ls’.
1356316Enabling Change Tracking for a temporal history table ‘%.*ls’ is not allowed.
1356416Adding CHECK constraint to a temporal history table ‘%.*ls’ is not allowed.
1356516Foreign key ‘%.*ls’ is not valid. A temporal history table cannot be used in a foreign key definition.
1356616Temporal table ‘%.*ls’ is already in use.
1356716Temporal history table ‘%.*ls’ cannot be created in a ‘tempdb’ database.
1356816System-versioned temporal table ‘%.*ls’ cannot be created in a ‘tempdb’ database.
1356916Cannot create a trigger on a system-versioned temporal table ‘%.*ls’.
1357016The use of replication is not supported with system-versioned temporal table ‘%s’
1357116Enabling Change Data Capture for a temporal history table ‘%ls’ is not allowed.
1357216Creating table variables containing PERIOD is not allowed.
1357316Setting SYSTEM_VERSIONING to ON failed because history table ‘%.*ls’ contains overlapping records.
1357416Setting SYSTEM_VERSIONING to ON failed because temporal history table ‘%.*ls’ contains SYSTEM_TIME period.
1357516ADD PERIOD FOR SYSTEM_TIME failed because table ‘%.*ls’ contains records where end of period is not equal to MAX datetime.
1357616DML operations are not allowed because system-versioned temporal table ‘%.*ls’ is in read-only mode.
1357716ALTER TABLE SWITCH statement failed on table ‘%.*ls’ because target table has SYSTEM_TIME PERIOD while source table does not have it.
1357816ALTER TABLE SWITCH statement failed on table ‘%.*ls’ because target and source tables have different SYSTEM_TIME PERIOD definitions.
1357916Setting SYSTEM_VERSIONING to ON failed because column ‘%.*ls’ does not use identical encryption in tables ‘%.*ls’ and ‘%.*ls’.
1358016Setting SYSTEM_VERSIONING to ON failed because history table ‘%.*ls’ has ROWGUID column specification. Consider dropping all ROWGUID column specifications and trying again.
1358116Setting SYSTEM_VERSIONING to ON failed because column ‘%.*ls’ does not have the same masking functions in tables ‘%.*ls’ and ‘%.*ls’.
1358216Setting SYSTEM_VERSIONING to ON failed because table ‘%.*ls’ has a FOREIGN KEY with cascading DELETE or UPDATE.
1358316Cannot add UNIQUE KEY constraint to a temporal history table ‘%.*ls’.
1358416Flush has not been executed for table because appropriate lock could not be obtained or it does not exist anymore.
1358516Computed column is defined with a user-defined function which is not allowed with system-versioned table ‘%.*ls’ because it performs user or system data access, or is assumed to perform this access. A function is assumed by default to perform data access if it is not schemabound.
1358616Temporal FOR SYSTEM_TIME clause cannot be used on remote data source ‘%.*ls’.
1358716Period column ‘%.*ls’ in a system-versioned temporal table cannot be nullable.
1358816Column ‘%.*ls’ in table ‘%.*ls’ cannot be dropped because it is a part of period definition.
1358916Column ‘%.*ls’ in table ‘%.*ls’ cannot be specified as ‘GENERATED ALWAYS’ in ALTER COLUMN statement.
1359016Temporal FOR SYSTEM_TIME clause can only be set once per temporal table. ‘%.*ls’ has more than one temporal FOR SYSTEM_TIME clause.
1359116SYSTEM_VERSIONING is not turned ON for table ‘%.*ls’.
1359216Cannot drop SYSTEM_TIME period from table ‘%.*ls’ when SYSTEM_VERSIONING is ON.
1359316SYSTEM_TIME period cannot be dropped from table ‘%.*ls’, because SYSTEM_TIME period does not exist.
1359416Table ‘%.*ls’ does not contain SYSTEM_TIME period ‘%.*ls’.
1359516Temporal history table name ‘%.*ls’ is not correct for current table ‘%.*ls’.
1359616SYSTEM_VERSIONING is already turned ON for table ‘%.*ls’.
1359716Temporal SYSTEM_TIME period is already defined on table ‘%.*ls’.
1359816Temporal SYSTEM_TIME period cannot be defined on history table ‘%.*ls’.
1359916Period column ‘%.*ls’ in a system-versioned temporal table cannot be altered.
1360016FOR JSON AUTO requires at least one table for generating JSON objects. Use FOR JSON PATH or add a FROM clause with a table name.
1360116Property ‘%.*ls’ cannot be generated in JSON output due to a conflict with another column name or alias. Use different names and aliases for each column in SELECT list.
1360216The FOR JSON clause is not allowed in a %ls statement.
1360316Property ‘%.*ls’ cannot be generated in JSON output due to invalid character in the column name or alias. Column name or alias that contains ‘..’, starts or ends with ‘.’ is not allowed in query that has FOR JSON clause.
1360416FOR JSON cannot serialize CLR objects. Cast CLR types explicitly into one of the supported types in FOR JSON queries.
1360516Column expressions and data sources without names or aliases cannot be formatted as JSON text using FOR JSON clause. Add alias to the unnamed column or table.
1360616JSON text that has more than 128 nesting levels cannot be parsed.
1360716JSON path is not properly formatted. Unexpected character ‘%lc’ is found at position %d.
1360816Property cannot be found on the specified JSON path.
1360916JSON text is not properly formatted. Unexpected character ‘%lc’ is found at position %d.
1361016The argument %d of the “%.*ls” must be a string literal.
1361116Value referenced by JSON path is not an array or object and cannot be opened with OPENJSON.
1361216Cannot convert a string value found in the JSON text to binary value because it is not Base64 encoded.
1361316Base64 encoded string cannot be converted to binary value. Binary data would be truncated.
1361416TEXT, NTEXT, SQL_VARIANT and IMAGE types cannot be used as column types in OPENJSON function with explicit schema. These types are not supported in WITH clause.
1361516OPENJSON function cannot convert value found in the JSON text to sql_variant data type. The value found in JSON text would be truncated.
1361616CLR types cannot be used as column types in OPENJSON function with explicit schema. CLR types are not supported in WITH clause.
1361716Table types cannot be used as column types in OPENJSON function with explicit schema. This type is not supported in WITH clause.
1361816AS JSON option can be specified only for column of nvarchar(max) type in WITH clause.
1361916Unsupported JSON path found in argument %d of JSON_MODIFY.
1362016ROOT option and WITHOUT_ARRAY_WRAPPER option cannot be used together in FOR JSON. Remove one of these options.
1362116Array cannot be found in the specified JSON path.
1362216An invalid value was specified for argument %d.
1362316Scalar value cannot be found in the specified JSON path.
1362416Object or array cannot be found in the specified JSON path.
1362516String value in the specified JSON path would be truncated.
1362616Openjson cannot have more than %d columns in with clause.
1370116System-versioned table schema modification failed because history table ‘%.*ls’ has custom unique keys defined. Consider dropping all unique keys and trying again.
1370216System-versioned table schema modification failed because history table ‘%.*ls’ has foreign keys defined. Consider dropping all foreign keys and trying again.
1370316System-versioned table schema modification failed because history table ‘%.*ls’ has table or column constraints defined. Consider dropping all table and column constraints and trying again.
1370416System-versioned table schema modification failed because history table ‘%.*ls’ has IDENTITY column specification. Consider dropping all IDENTITY column specifications and trying again.
1370516System-versioned table schema modification failed because history table ‘%.*ls’ has computed column specification. Consider dropping all computed column specifications and trying again.
1370616System-versioned table schema modification failed because history table ‘%.*ls’ is not available or it is placed on a read-only file group.
1370716System-versioned table schema modification failed because history table ‘%.*ls’ is configured for change data capture. Consider dropping this configuration and trying again.
1370816System-versioned table schema modification failed because history table ‘%.*ls’ has triggers defined. Consider dropping all triggers and trying again.
1370916System-versioned table schema modification failed because table ‘%.*ls’ has %d columns and table ‘%.*ls’ has %d columns.
1371016System-versioned table schema modification failed because column ‘%.*ls’ at ordinal %d in history table ‘%.*ls’ has a different name than the column ‘%.*ls’ at the same ordinal in table ‘%.*ls’.
1371116System-versioned table schema modification failed because column ‘%.*ls’ has data type %s in history table ‘%.*ls’ which is different from corresponding column type %s in table ‘%.*ls’.
1371216System-versioned table schema modification failed because column ‘%.*ls’ does not have the same collation in tables ‘%.*ls’ and ‘%.*ls’.
1371316System-versioned table schema modification failed because column ‘%.*ls’ does not have the same CLR type in tables ‘%.*ls’ and ‘%.*ls’.
1371416System-versioned table schema modification failed because column ‘%.*ls’ does not have the same ANSI trimming semantics in tables ‘%.*ls’ and ‘%.*ls’.
1371516System-versioned table schema modification failed because column ‘%.*ls’ does not have the same XML Schema Collection in tables ‘%.*ls’ and ‘%.*ls’.
1371616System-versioned table schema modification failed because system column ‘%.*ls’ in history table ‘%.*ls’ corresponds to a period column in table ‘%.*ls’ and cannot be nullable.
1371716System-versioned table schema modification failed because column ‘%.*ls’ does not have the same nullability attribute in tables ‘%.*ls’ and ‘%.*ls’.
1371816System-versioned table schema modification failed because system-versioned tables cannot have FILESTREAM columns.
1371916System-versioned table schema modification failed because column ‘%.*ls’ does not have the same sparse storage attribute in tables ‘%.*ls’ and ‘%.*ls’.
1372016System-versioned table schema modification failed because column ‘%.*ls’ does not have the same column set property in tables ‘%.*ls’ and ‘%.*ls’.
1372116System-versioned table schema modification failed because temporal history table ‘%.*ls’ contains SYSTEM_TIME period.
1372216Computed column is defined with a user-defined function which is not allowed with system-versioned table ‘%.*ls’ because it performs user or system data access, or is assumed to perform this access. A function is assumed by default to perform data access if it is not schemabound.
1372316System-versioned table schema modification failed because history table ‘%.*ls’ has ROWGUID column specification. Consider dropping all ROWGUID column specifications and trying again.
1372416System-versioned table schema modification failed because adding computed column while system-versioning is ON is not supported.
1372516System-versioned table schema modification failed because column ‘%.*ls’ does not have the same masking functions in tables ‘%.*ls’ and ‘%.*ls’.
1372616Setting SYSTEM_VERSIONING to ON failed because history table ‘%.*ls’ is referenced by one or more BLOCK security predicates. Consider removing the BLOCK security predicates referencing this table and trying again.
1372716Temporal ‘GENERATED ALWAYS AS %ls’ column ‘%.*ls’ has invalid data type.
1372816Temporal ‘GENERATED ALWAYS AS %ls’ column ‘%.*ls’ cannot be nullable.
1372916Temporal ‘GENERATED ALWAYS’ column ‘%.*ls’ cannot be altered.
1373016Setting SYSTEM_VERSIONING to ON failed because column ‘%.*ls’ in history table ‘%.*ls’ corresponds to a generated always column in table ‘%.*ls’ and cannot be nullable.
1373116System-versioned table schema modification failed because column ‘%.*ls’ in history table ‘%.*ls’ corresponds to a generated always column in table ‘%.*ls’ and cannot be nullable.
1373216Temporal ‘GENERATED ALWAYS AS %ls’ column ‘%.*ls’ has invalid data length.
1373316Temporal table cannot have more than one ‘GENERATED ALWAYS AS %ls’ column.
1373416System-versioned table schema modification failed because online alter is not supported on system-versioned memory optimized table ‘%.*ls’.
1373516Cannot alter HIDDEN attribute on column ‘%.*ls’ in table ‘%.*ls’ because this column is not a generated always column.
1373616ALTER TABLE SWITCH statement failed on table ‘%.*ls’ because column ‘%.*ls’ does not have the same GENERATED ALWAYS attribute in target and source tables.
1373816History table ‘%.*ls’ can not be memory optimized table.
1373916Memory optimized temporal table ‘%.*ls’ must be created with DURABILITY set to SCHEMA_AND_DATA.
1374016The row size limit of %d bytes for memory optimized system versioned tables has been exceeded. Please simplify the table definition.
1374116Cannot create UNIQUE index on temporal history table ‘%.*ls’.
1374216Table ‘%.*ls’ contains records where ‘GENERATED ALWAYS AS %ls’ is not equal to %ls.
1374316%ld is not a valid value for system versioning history retention period.
1374416‘%.*ls’ is not a valid history retention period unit for system versioning.
1374516System-versioned table schema modification failed because column ‘%.*ls’ does not use identical encryption in tables ‘%.*ls’ and ‘%.*ls’.
1374616‘%.*ls’ is not a system versioned temporal table.
1374716Cannot apply history cleanup on table ‘%.*ls’ because it has infinite retention period.
1374816Setting SYSTEM_VERSIONING to ON failed because table ‘%.*ls’ exceeds the maximum of 1023 columns.
1374916The period of %ld %S_MSG is too big for system versioning history retention.
1375016Temporal period column ‘%.*ls’ does not exist.
1375116Temporal application time column ‘%.*ls’ has invalid data type. Allowed data types are datetime2, smalldatetime, datetimeoffset, date and datetime.
1375216Column ‘%.*ls’ must be defined as NOT NULL in order to be used in a temporal application time period.
1375316Temporal period columns cannot have different data types.
1375416Temporal period columns cannot have different data type precision.
1375516Temporal period ‘%.*ls’ has the same start and end time column.
1375616Column ‘%.*ls’ is used in the temporal period ‘%.*ls’ and cannot be explicitly placed in the key list of a constraint where that same period without overlaps is used.
1375716Temporal table ‘%.*ls’ already has history table defined. Consider dropping system_versioning first if you want to use different history table.
1375816Cannot define foreign key constraint ‘%.*ls’ with cascaded DELETE or UPDATE on table ‘%.*ls’ because table is system-versioned.
1375916Renaming a column failed on history table ‘%ls’ because it is not a supported operation on system-versioned tables. Consider setting SYSTEM_VERSIONING to OFF and trying again.
1376016Accessing history table for memory optimized temporal table using the SERIALIZABLE isolation level is not supported while SYSTEM_VERSIONING is ON.
1376116The hint ‘%.*ls’ is not supported with history table for memory optimized temporal table while SYSTEM_VERSIONING is ON.
1376216Cannot alter temporal table ‘%.*ls’ because this operation is currently not available.
1376316Cannot query temporal table ‘%.*ls’ because this operation is currently not available.
1376416Online alter column is not supported for system-versioned temporal table ‘%.*ls’.
1376516Setting finite retention period failed on system-versioned temporal table ‘%.*ls’ because the history table ‘%.*ls’ does not contain required clustered index. Consider creating a clustered columnstore or B-tree index starting with the column that matches end of SYSTEM_TIME period, on the history table.
1376616Cannot drop the clustered index ‘%.*ls’ because it is being used for automatic cleanup of aged data. Consider setting HISTORY_RETENTION_PERIOD to INFINITE on the corresponding system-versioned temporal table if you need to drop this index.
1376716The clustered index ‘%.*ls’ is being used for automatic cleanup of aged data, and can be converted to either a clustered columnstore or B-tree index starting with the column that matches end of SYSTEM_TIME period, on the history table. Consider setting HISTORY_RETENTION_PERIOD to INFINITE on the corresponding system-versioned temporal table if you need to rebuild this index with a modified column specification, not supported with temporal history retention.
1376816Retention cleanup of history table for a temporal table (database id %lu, table id %ld) has not been executed. Either the cleanup is disabled on the database, appropriate lock could not be obtained or the temporal table does not exist anymore.
1376916Setting SYSTEM_VERSIONING to ON failed for table ‘%.*ls’ because ‘%.*ls’ with REMOTE_DATA_ARCHIVE enabled cannot be used as a history table when a finite retention period is specified.
1377016Setting finite retention period failed on system-versioned temporal table ‘%.*ls’ because REMOTE_DATA_ARCHIVE is enabled on the corresponding history table ‘%.*ls’.
1377116Setting finite retention period failed on system-versioned temporal table ‘%.*ls’ because corresponding history table ‘%.*ls’ has both clustered columnstore and non-clustered indexes. Consider dropping non-clustered indexes from the history table and try again.
1377216Cannot create non-clustered index on temporal history table ‘%.*ls’ since it has finite retention period and clustered columnstore index defined.
1377316Clustered column store temporal retention cleanup attempted on non-clustered column store table ‘%.*ls’.
1377416Setting SYSTEM_VERSIONING to ON failed because table ‘%.*ls’ has INSTEAD OF triggers defined. Consider dropping INSTEAD OF triggers and trying again.
1377516System-versioned table schema modification failed because table ‘%.*ls’ has INSTEAD OF triggers defined. Consider dropping INSTEAD OF triggers and trying again.
1377616Table ‘%.*ls’ does not exist or you do not have the required permissions to complete the operation.
1377716Stored procedure ‘sp_cleanup_temporal_history’ is temporarily disabled. Please contact customer support for more information.
1377816The only allowed ALTER TABLE operations on temporal in-memory history table ‘%.*ls’ are ADD INDEX, DROP INDEX and ALTER INDEX.
1377916Defining a column store index on temporal in-memory history table ‘%.*ls’ is not supported.
1378016Setting finite retention period failed on system-versioned temporal table ‘%.*ls’ beacause the history table ‘%.*ls’ is clustered column store that contains large object columns.
1378116Wrong type for column ‘%.*ls’: the system-versioned temporal table ‘%.*ls’ cannot contain large object columns, because it has finite retention and the clustered column store history table ‘%.*ls’.
1378216Cannot create clustered column store index ‘%.*ls’ on table ‘%.*ls’ because it contains large object columns and is the history table of temporal table ‘%.*ls’ that has finite retention.
1378316Data modification failed on system-versioned table ‘%.*ls’ because column ‘%.*ls’ cannot be output into the history table ‘%.*ls’.
1378416Setting SYSTEM_VERSIONING to ON failed because column ‘%.*ls’ does not have the same sensitivity classification in tables ‘%.*ls’ and ‘%.*ls’.
1378516System-versioned table schema modification failed because column ‘%.*ls’ does not have the same sensitivity classification in tables ‘%.*ls’ and ‘%.*ls’.
1379516‘%.*ls’ does not exist, or is not a temporal application time period.
1379616Temporal application time period without overlaps can be defined only on a primary key or a unique constraint.
1379716Temporal application time period is already defined on table ‘%.*ls’.
1379816A table cannot have more than one application time period definition.
1379916‘%.*ls’ is not allowed as application time period name.
1380016INSERT BULK statement does not support recompile.
1380116TEXT, NTEXT, SQL_VARIANT and IMAGE types cannot be used as column types in OPENROWSET function with inline schema. These types are not supported in WITH clause.
1380216CLR types cannot be used as column types in OPENROWSET function with inline schema. These types are not supported in WITH clause.
1380316Table types cannot be used as column types in OPENROWSET function with inline schema. These types are not supported in WITH clause.
1380416Invalid escape character specified for bulk load. Escape character can be one single byte or Unicode character.
1380517An internal error has occurred during wildcard expansion.
1380616It is not possible to expand wildcards in path to provided data source.
1380716Content of directory on path ‘%ls’ cannot be listed.
1380816Starting offset cannot be larger than the file size.
1380910Warning: No datasets were found that match the expression ‘%ls’.
1381016Column ‘%ls’ is of type ‘%ls’ which is not supported with file format ‘%ls’.
1381116Bulk load data conversion error (truncation) for row %d, column %d (%ls) in data file %ls.
1381216Bulk load data conversion error (type mismatch or invalid character for the specified codepage) for row %d, column %d (%ls) in data file %ls.
1381316Bulk load data conversion error (overflow) for row %d, column %d (%ls) in data file %ls.
1381416Bulk load failed: Data file %ls does not have %ls encoding.
1390016Identifier ‘%.*ls’ in a MATCH clause could not be bound.
1390116Identifier ‘%.*ls’ in a MATCH clause is not a node table or an alias for a node table.
1390216Identifier ‘%.*ls’ in a MATCH clause is not an edge table or an alias for an edge table.
1390316Edge table ‘%.*ls’ used in more than one MATCH pattern.
1390416All node and edge tables within a single MATCH clause must reside in the same database.
1390516A MATCH clause may not be directly combined with other expressions using OR or NOT.
1390616Node table name or alias ‘%.*s’ marked as FOR PATH cannot be used outside the recursive section of a SHORTEST_PATH clause except in a LAST_NODE function.
1390716Cannot modify permissions for graph column ‘%.*s’.
1390816Cannot access internal graph column ‘%.*ls’.
1390916The internal graph column ‘%.*ls’ cannot be added to an index; use pseudocolumn ‘%.*ls’ instead.
1391016Cannot create a node or edge table as memory optimized.
1391116Cannot create a node or edge table as a remote data archive.
1391216A node or edge table cannot be created as or altered to a temporal table.
1391316Internal graph columns cannot be altered.
1391416Cannot create a node or edge table as a temporary table.
1391516Cannot create a node or edge table as an external table.
1391616The graph column ‘%.*ls’ cannot be used as a non-key column in an index or as a partitioning column.
1391716After expanding the computed graph column ‘%.*ls”, the index ‘%.*ls’ on table ‘%.*ls’ exceeds the maximum number of columns in the key list. The maximum number of index key columns is %d.
1391816Adding constraint to column ‘%.*s’ of a node or edge table is not allowed.
1391916Identifier ‘%.*ls’ in a MATCH clause corresponds to a derived table. Derived tables are not supported in MATCH clauses.
1392016Identifier ‘%.*ls’ in a MATCH clause is used with a JOIN clause or APPLY operator. JOIN and APPLY are not supported with MATCH clauses.
1392116JSON data for INSERT/UPDATE of graph pseudocolumn ‘%.*ls’ is malformed.
1392216Remote tables are not supported in MATCH clauses.
1392316Pseudocolumn ‘%.*s’ is invalid because it references a node or edge table that is not in the current database.
1392416Select * is not permitted because it refers to a node or edge table ‘%.*s’ which is not in the current database.
1392516Cannot drop or disable index or constraint ‘%.*s’ because the last unique index or constraint on ‘%.*s’ cannot be dropped or disabled.
1392616The use of replication is not supported for node or edge table ‘%ls’.
1392716Change Data Capture is not supported for node or edge table ‘%ls’.
1392816Use pseudocolumn ‘%.*ls’ to add a constraint on a node or edge table.
1392916The pseudocolumn ‘%.*ls’ cannot be part of an index unless the index is on a node or edge table that contains that pseudocolumn.
1393016Edge constraint cannot be created on table ‘%.*ls’.  The table is not an edge table.
1393116Edge constraint ‘%.*ls’ references invalid table ‘%.*ls’.  Table could not be found.
1393216Cross-database edge constraints are not supported.
1393316Edge constraint must reference node tables.
1393416Could not drop node table ‘%.*ls’ because it is referenced by an edge constraint.
1393516Cannot enable edge constraint ‘%.*ls’ as there are no online, unique, unfiltered $node_id indexes on one or more target node tables.
1393610Warning: Edge constraint ‘%.*ls’ on table ‘%.*ls’ was disabled as a result of disabling the index ‘%.*ls’.
1393716Cannot disable clustered index ‘%.*ls’ on table ‘%.*ls’. Permission denied to disable edge constraint ‘%.*ls’ on table ‘%.*ls’ that references this table.
1393816The target table ‘%.*ls’ of the INSERT statement cannot be on either side of an edge constraint relationship when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. Found edge constraint ‘%.*ls’.
1393915The target table ‘%.*ls’ of the OUTPUT INTO clause cannot be on either side of an edge constraint relationship. Found edge constraint ‘%.*ls’.
1394016Cannot use a derived table ‘%.*ls’ in a MATCH clause.
1394116Cannot create an edge constraint that references a node table with a disabled $node_id index.
1394216The initial recursive quantifier must be 1: {1, … }.
1394316The final recursive quantifier must be greater than the initial recursive quantifier.
1394416Cannot truncate table ‘%.*ls’ because it is being referenced by an EDGE constraint.
1394516Cannot delete from a node table that is the target of both an edge constraint and a foreign key constraint on the $node_id column.
1394616Cannot create a foreign key constraint referencing the $node_id or $edge_id column of a graph table.
1394716Merge statements containing a MATCH clause do not support derived tables or views in the MATCH clause.
1394816The table name or alias ‘%.*s’ must be marked as FOR PATH to be used in the recursive section of a SHORTEST_PATH clause.
1394916The table name or alias ‘%.*s’ was marked as FOR PATH but was not used in the recursive section of a SHORTEST_PATH clause.
1395016Node table name or alias ‘%.*ls’ was used more than once in a SHORTEST_PATH recursive section.
1395116Aggregate function ‘%ls’ is not supported with WITHIN GROUP (GRAPH PATH).
1395216No columns in the aggregate ‘%ls’ WITHIN GROUP(GRAPH PATH) reference a recursive path.
1395316Columns in the aggregate ‘%ls’ WITHIN GROUP(GRAPH PATH) reference more than one recursive path.
1395416Identifier ‘%.*ls’ in aggregate ‘%ls’ WITHIN GROUP(GRAPH PATH) is not referencing a recursive path and cannot be used.
1395516Recursive MATCH queries cannot be used in a table-valued function.
1395616Recursive MATCH queries cannot be used on the right side of APPLY.
1395716Recursive MATCH queries cannot be used in subqueries.
1395816Internal Error: Unable to compile MATCH query with derived table or view ‘%.*ls’.
1395916Introducing edge constraint ‘%.*ls’ on table ‘%.*ls’ may cause cycles or multiple cascade paths. Specify ON DELETE NO ACTION or modify other constraints.
1396016Cannot define edge constraint ‘%.*ls’ with cascaded DELETE on table ‘%.*ls’ because the table has an INSTEAD OF DELETE TRIGGER defined on it.
1396116The alias or identifier ‘%.*ls’ cannot be used in the select list, order by, group by, or having context.
1396216The alias or identifier ‘%.*ls’ is not the last node in a shortest path pattern. Only the last node in the path can be used with LAST_NODE().
1396316Node table name or alias ‘%.*s’ refers to a derived table and cannot be used by the LAST_NODE function.
1396416The two aliases ‘%.*s’ and ‘%.*s’ refer to different underlying objects in a LAST_NODE equality expression.
1396516The table name or alias ‘%.*s’ must use the LAST_NODE function to reference the last node in a shortest_path expression.
1396616A recursive quantifier expression exceeds the limit of %d. Consider the ‘+’ syntax instead.
1396716Pseudocolumn ‘%.*ls’ is not supported for use as a partitioning column on a table or index.
1396816An explicit DROP INDEX is not allowed on index ‘%.*ls’. It is being used for edge constraint enforcement.

Leave a Reply

You May Also Like

When dealing with a relational database management system (RDBMS) like SQL Server, compatibility level is an important concept to understand....
In this blog post, let’s learn about the error message “49975 – Unable to load controller client certificate due to...
In this blog post, let’s learn about the error message “49973 – Cannot remove tempdb remote file to local tempdb...