A scheduled job step ran DBCC CHECKTABLE on a table but returned the following error:
Cannot continue the execution because the session is in the kill state. [SQLSTATE HY000] (Error 596). The step failed.
What causes this error?
DBCC CHECKTABLE Kill State Error – Causes of ‘Session is in the Kill State’ Error in DBCC CHECKTABLE
dbcc-checktablesql serversql server 2014
Related Question
- SQL Server – Stack Dumps When Enabling Temporal Table SYSTEM_VERSIONING
- Sql-server – how to check who has killed the job which was running ?if logs are not generated
- Sql-server – Getting error running DBCC Checktable(tablename, repair_allow_data_loss)
- SQL Server – Handling Persisted Computed CLR Data with DBCC CHECKTABLE
- SQL Server 2016 – Resolving DBCC Failures Due to AlwaysOn State Changes
- Sql-server – DatabaseIntegrityCheck Fails on Large Database Every Day
- Sql-server – “Cannot continue the execution because the session is in the kill state” Error
Best Answer
Many things cause a session to enter a kill state. If other user kills your session, or if running command throws an error which severity needs terminate the connection (check this for more info https://docs.microsoft.com/en-us/sql/relational-databases/errors-events/database-engine-error-severities?view=sql-server-ver15)
When CHECK* commands result in this, ins most cases is because it triggers some error with severity 19 or higher. Can be your table corrupted or just a space problem. You must investigate further to more details.