Error codes
17,238
Database Engine error numbers
sql server / error codes
SQL Server
error codes.
Look up SQL Server Database Engine error numbers, messages, severity, event logging, and Microsoft source links.
Search by code or message text. Use severity and event logging to decide where to check next.
Event logged
1,430
Marked by SQL Server for event logging
Microsoft pages
344
Errors with a dedicated source page
Updated
May 7, 2026
73,354 source rows parsed
Search
Find an SQL Server error code
Search by number, severity, category, or message text.
17,238 codes
Type at least two characters to show matching error codes.
How to use this lookup
Start with the exact code
Search for the SQL Server error number first. Message text can vary slightly between versions and applications.
Check severity
Severity shows how SQL Server classified the message. Higher severity usually needs faster review, especially 20 and above.
Use the source link
Open the Microsoft source for the matching error or range when you need the official message text.
Common error codes
Common SQL Server error codes
Common SQL Server errors found in application logs, SQL Agent jobs, deployment output, backups, and the SQL Server error log.
ErrorMessageSeverityCategorySource
Error 102
Incorrect syntax near '%.*ls'.
Severity 15
Syntax or query shape
Error 207
Invalid column name '%.*ls'.
Severity 16
Syntax or query shape
Error 208
Invalid object name '%.*ls'.
Severity 16
Syntax or query shape
Error 229
The %ls permission was denied on the object '%.*ls', database '%.*ls', schema '%.*ls'.
Severity 14
Security or permissions
Error 245
Conversion failed when converting the %ls value '%.*ls' to data type %ls.
Severity 16
Version or change risk
Error 2627
Violation of %ls constraint '%.*ls'. Cannot insert duplicate key in object '%.*ls'. The duplicate key value is %ls.
Severity 14
Security or permissions
Error 1205
Transaction (Process ID %d) was deadlocked on %.*ls resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
Severity 13
Deadlock
Error 18456
Login failed for user '%.*ls'.%.*ls%.*ls
Severity 14
Security or permissions
Error 823
The operating system returned error %ls to SQL Server during a %S_MSG at offset %#016I64x in file '%ls'. Additional messages in the SQL Server error log and operating system error log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Severity 24
Corruption or engine risk
Error 824
SQL Server detected a logical consistency-based I/O error: %ls. It occurred during a %S_MSG of page %S_PGID in database ID %d at offset %#016I64x in file '%ls'. Additional messages in the SQL Server error log or operating system error log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see [https://go.microsoft.com/fwlink/?linkid=2252374](https://go.microsoft.com/fwlink/?linkid=2252374).
Severity 24
Corruption or engine risk
Error 825
A read of the file '%ls' at offset %#016I64x succeeded after failing %d time(s) with error: %ls. Additional messages in the SQL Server error log and operating system error log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Severity 10
Corruption or engine risk
Error 9002
The transaction log for database '%ls' is full due to '%ls' and the holdup lsn is %S_LSN.
Severity 17
Resource pressure
Categories
SQL Server error categories
Use these categories to narrow the lookup when you know the type of problem, such as login failures, syntax errors, backup failures, resource pressure, or corruption warnings.
General engine error
7,332 errors
General engine errors cover messages that do not fit a narrower bucket. Use the exact error number, message text, severity, and timestamp to continue the lookup.
Examples #165 #184 #187 #192
Syntax or query shape
2,321 errors
Syntax and query-shape errors usually come from invalid T-SQL, object names, columns, variables, identifiers, procedures, functions, or generated SQL.
Examples #102 #207 #208 #101
Security or permissions
1,696 errors
Security and permission errors include login failures, denied access, credential problems, certificates, principals, users, and permission checks.
Examples #229 #2627 #18456 #218
Availability
1,349 errors
Availability-related SQL Server errors usually mention replicas, failover, endpoints, mirroring, clustering, listeners, or Always On state.
Examples #341 #369 #548 #666
Resource pressure
1,202 errors
Resource-pressure errors point toward disk, log space, tempdb, memory, worker threads, quotas, limits, or full database files.
Examples #9002 #103 #105 #106
Performance or concurrency
1,040 errors
Performance and concurrency errors often involve locks, blocking, query execution, statistics, workers, waits, or plan-related behavior.
Examples #159 #172 #288 #304
Version or change risk
874 errors
Version and change-risk errors usually appear when a feature, compatibility level, edition, deprecated behavior, or SQL Server version does not match the workload.
Examples #245 #125 #206 #210
Corruption or engine risk
749 errors
Corruption or engine-risk errors include high-severity I/O, checksum, consistency, DBCC, and storage-related messages that should be handled carefully.
Examples #823 #824 #825 #21
Backup and restore
664 errors
Backup and restore errors usually need the full job output, backup chain, file path, media, database state, and restore target checked together.
Examples #667 #805 #908 #922
Deadlock
11 errors
Deadlock errors mean SQL Server picked a victim because two or more sessions blocked each other in a lock cycle. The deadlock graph is the useful evidence.
Examples #1205 #1231 #3635 #5231
Number ranges
SQL Server error number ranges
Microsoft groups Database Engine errors by number range. Use these source pages when you know the error number and need the official range.
RangeCodesSource
Errors 0 to 999677 codesErrors 1,000 to 1,999486 codesErrors 2,000 to 2,999396 codesErrors 3,000 to 3,999578 codesErrors 4,000 to 4,999496 codesErrors 5,000 to 5,999497 codesErrors 6,000 to 6,999532 codesErrors 7,000 to 7,999502 codesErrors 8,000 to 8,999625 codesErrors 9,000 to 9,999613 codesErrors 10,000 to 10,999416 codesErrors 11,000 to 12,999681 codesErrors 13,000 to 13,999735 codesErrors 14,000 to 14,999648 codesErrors 15,000 to 15,999653 codesErrors 16,000 to 17,999557 codesErrors 18,000 to 18,999269 codesErrors 19,000 to 20,999802 codesErrors 21,000 to 21,999790 codesErrors 22,000 to 22,999702 codesErrors 23,000 to 25,999466 codesErrors 26,000 to 27,999371 codesErrors 28,000 to 30,999477 codesErrors 31,000 to 41,3992,426 codesErrors 41,400 to 49,9991,843 codes