SQL Server error codes

• 1205Transaction (Process ID) was deadlocked on lock resources with another process and has been chosen as the deadlock victim
• 2627Violation of PRIMARY KEY / UNIQUE KEY constraint. Cannot insert duplicate key in object
• 2601Cannot insert duplicate key row in object with unique index. The duplicate key value is ...
• 547The INSERT/UPDATE/DELETE statement conflicted with the FOREIGN KEY / CHECK constraint
• 18456Login failed for user
• 8152String or binary data would be truncated
• 2628String or binary data would be truncated in table, column ...; truncated value
• 1222Lock request time out period exceeded
• 9002The transaction log for database is full due to ...
• 1105Could not allocate space for object in database because the filegroup is full
• 208Invalid object name
• 229The SELECT/EXECUTE permission was denied on the object
• 4060Cannot open database requested by the login. The login failed
• 233A connection was successfully established with the server, but then an error occurred (no process is on the other end of the pipe)
• 823The operating system returned error to SQL Server during a read/write at offset in file (I/O error)
• 824SQL Server detected a logical consistency-based I/O error (page corruption)
• 701There is insufficient system memory in resource pool to run this query
• 845Time-out occurred while waiting for buffer latch
• 3201Cannot open backup device. Operating system error (backup device error)
• 8134Divide by zero error encountered
• 245Conversion failed when converting the value to data type
• 515Cannot insert the value NULL into column
• 8115Arithmetic overflow error converting expression to data type
• 512Subquery returned more than 1 value
• 207Invalid column name
• 156Incorrect syntax near the keyword
• 2812Could not find stored procedure
• 8623The query processor ran out of internal resources and could not produce a query plan
• 4104The multi-part identifier could not be bound
• 2714There is already an object named in the database
• 601Could not continue scan with NOLOCK due to data movement
• 50000Custom error raised with RAISERROR
• 3902The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION
• 1101Could not allocate a new page because of insufficient disk space in filegroup
• 3729Cannot DROP because it is being referenced by object
• 3961Snapshot isolation transaction failed because the object was modified by a DDL statement
• 1785Introducing FOREIGN KEY constraint may cause cycles or multiple cascade paths
• 9421XML parsing: illegal xml character
• 15151Cannot find the object/principal because it does not exist or you do not have permission
• 4834You do not have permission to use the bulk load statement
• 10928Resource limit for the database has been reached (Azure SQL)
• 40544The database has reached its size quota (Azure SQL)
• 40613Database is not currently available (Azure SQL)
• 102Incorrect syntax near 'token'
• 8114Error converting data type X to Y
• 1204The instance of the SQL Server Database Engine cannot obtain a LOCK resource
• 3906Failed to update database because the database is read-only
• 15023User already exists in the current database
• 18452Login failed. The login is from an untrusted domain and cannot be used with Windows authentication
• 605Attempt to fetch logical page belongs to a different allocation unit
• 4922ALTER TABLE ALTER COLUMN failed because one or more objects access this column
• 7202Could not find server 'name' in sys.servers
• 40501The service is currently busy. Retry the request after 10 seconds
• 8645A time out occurred while waiting for memory resources to execute the query
• 8651Could not perform the operation because the requested memory grant was not available
• 5061ALTER DATABASE failed because a lock could not be placed on database
• 3702Cannot drop database because it is currently in use
• 15138The database principal owns a schema in the database, and cannot be dropped
• 1934INSERT/UPDATE failed because the following SET options have incorrect settings
• 468Cannot resolve the collation conflict
• 4864Bulk load data conversion error (type mismatch or invalid character)
• 916The server principal is not able to access the database under the current security context