OPERATIONAL DEFECT DATABASE
...
...
Assume that you enable Trace Flag 176 in Microsoft SQL Server. When you run a query on a table that has persisted computed columns, SQL Server generates an Access violation. Additionally, you may receive one or both of the following error messages: Msg 596, Level 21, State 1, Line LineNumber Cannot continue the execution because the session is in the kill state. or Msg 0, Level 20, State 0, Line LineNumber A severe error occurred on the current command. The results, if any, should be discarded. Additionally, the SQL Server error log will report an Access Violation, and a dump file will be generated in the log file folder.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This issue is fixed in the following cumulative updates for SQL Server: Cumulative Update 4 for SQL Server 2019 Cumulative Update 20 for SQL Server 2017 Cumulative Update 12 for SQL Server 2016 SP2 About cumulative updates for SQL Server: Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server: Latest cumulative update for SQL Server 2019 Latest cumulative update for SQL Server 2017 Latest cumulative update for SQL Server 2016
Learn about the terminology that Microsoft uses to describe software updates.
Click on a version to see all relevant bugs
Microsoft SQL Server Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
