SQL Server 오류 코드

• 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 (데이터 이동으로 NOLOCK 스캔을 계속할 수 없음)
• 50000Custom error raised with RAISERROR (RAISERROR로 발생시킨 사용자 정의 오류)
• 3902The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION (대응하는 BEGIN TRANSACTION이 없는 COMMIT TRANSACTION)
• 1101Could not allocate a new page because of insufficient disk space in filegroup (파일 그룹의 디스크 공간 부족으로 새 페이지를 할당할 수 없음)
• 3729Cannot DROP because it is being referenced by object (객체가 참조 중이어서 DROP 불가)
• 3961Snapshot isolation transaction failed because the object was modified by a DDL statement (객체가 DDL로 변경되어 스냅샷 격리 트랜잭션 실패)
• 1785Introducing FOREIGN KEY constraint may cause cycles or multiple cascade paths (FOREIGN KEY 제약 조건이 순환 또는 다중 cascade 경로를 만들 수 있음)
• 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 (bulk load 문을 사용할 권한 없음)
• 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 (SQL Server Database Engine 인스턴스가 LOCK 리소스를 확보할 수 없음)
• 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 (로그인 실패. 신뢰할 수 없는 도메인의 로그인은 Windows 인증에 사용할 수 없음)
• 605Attempt to fetch logical page belongs to a different allocation unit (가져오려는 논리 페이지가 다른 allocation unit에 속함)
• 4922ALTER TABLE ALTER COLUMN failed because one or more objects access this column (하나 이상의 객체가 이 컬럼에 접근하므로 ALTER TABLE ALTER COLUMN 실패)
• 7202Could not find server 'name' in sys.servers (sys.servers에서 서버를 찾을 수 없음)
• 40501The service is currently busy. Retry the request after 10 seconds (서비스가 현재 바쁨. 10초 후 재시도)
• 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 (요청한 memory grant를 사용할 수 없어 작업을 수행할 수 없음)
• 5061ALTER DATABASE failed because a lock could not be placed on database (데이터베이스에 락을 걸 수 없어 ALTER DATABASE 실패)
• 3702Cannot drop database because it is currently in use (사용 중이어서 데이터베이스 삭제 불가)
• 15138The database principal owns a schema in the database, and cannot be dropped (database principal이 스키마를 소유하고 있어 삭제 불가)
• 1934INSERT/UPDATE failed because the following SET options have incorrect settings (다음 SET 옵션의 설정이 잘못되어 INSERT/UPDATE 실패)
• 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 (서버 보안 주체가 현재 보안 컨텍스트에서 데이터베이스에 접근할 수 없음)