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?

  • 1
    Someone killed your job, you can check the error log and find out which computer did that. Commented Dec 18, 2020 at 11:01
  • 2
    other potential reasons: 1) lack of free space in tempdb; 2) failover of db (AAG case); 3) deadlock and checktable is the victim. Commented Dec 18, 2020 at 11:29
  • 1
    Check for an access violation in the SQL Server error log.
    – sqL_handLe
    Commented Dec 18, 2020 at 13:56

2 Answers 2


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://learn.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.


After poking around, discovered that the volume was very low on space so probably didn't meet the free space requirements for "dbcc checktable".

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.