Operational Defect Database
BugZero found this defect 1308 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Microsoft SQL Server | 10965984
KB4039966 - FIX: Access violation occurs when a DDL trigger is raised by the CREATE EXTERNAL TABLE command in SQL Server 2016 or 2017 - Microsoft Support
Last update date:
7/20/2023
Affected products:
SQL Server 2016 Developer - duplicate (do not use)
SQL Server 2016 Enterprise - duplicate (do not use)
SQL Server 2016 Enterprise Core - duplicate (do not use)
SQL Server 2016 Standard - duplicate (do not use)
SQL Server 2016 Service Pack 1
SQL Server 2017 on Windows (all editions)
Affected releases:
build lower than 14.0.3006.16
Fixed releases:
14.0.3006.16
Description:
Symptoms
Assume that you use PolyBase in Microsoft SQL Server 2016 or 2017, and you have a data definition language (DDL) trigger that occurs every time that a CREATE EXTERNAL TABLE command is run. When you run the CREATE EXTERNAL TABLE command to create a PolyBase external table, an access violation (AV) may occur because of the DDL trigger that's raised. Additionally, you may receive error messages that resemble the following: Msg 596, Level 21, State 1, Line LineNumber Cannot continue the execution because the session is in the kill state. Msg 0, Level 20, State 0, Line LineNumber A severe error occurred on the current command. The results, if any, should be discarded.
Resolution
This issue is fixed in the following cumulative updates for SQL Server: Cumulative Update 1 for SQL Server 2017 Cumulative Update 8 for SQL Server 2016 RTM Cumulative Update 5 for SQL Server 2016 SP1
