0

We enabled temporal data (system-versioning history for table) on SQL Server 2017 but when we execute a delete command like below get an error message

Cannot continue the execution because the session is in the kill state 

delete kelakets where id=5

but when we disable the history table for main table and related tables, then execute the delete command it works perfect and nicely.

Disable history command: 

ALTER TABLE Kelakets SET (SYSTEM_VERSIONING = OFF);
ALTER TABLE tableRelated1 SET (SYSTEM_VERSIONING = OFF);
ALTER TABLE tableRelated2 SET (SYSTEM_VERSIONING = OFF);
Dale K
  • 25,246
  • 15
  • 42
  • 71
sajjad
  • 646
  • 1
  • 9
  • 20
  • 1
    Check the SQL Server error log for related messages. – Dan Guzman Jun 16 '20 at 10:09
  • @DanGuzman sql log : Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION Access Violation occurred reading address 000000000000000C Input Buffer 86 bytes - – sajjad Jun 16 '20 at 11:24
  • This could be corruption or a SQL Server bug. Run DBCC to rule out the former, and if clean, create a simplified script that recreates the problem and report on the [feedback site](https://feedback.azure.com/forums/908035-sql-server). – Dan Guzman Jun 16 '20 at 12:23
  • @DanGuzman CHECKDB report : CHECKDB found 0 allocation errors and 0 consistency errors in database – sajjad Jun 16 '20 at 13:14

0 Answers0