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

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 2017

Latest cumulative update for SQL Server 2016

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References

Learn about the terminologythat Microsoft uses to describe software updates.

Har du brug for mere hjælp?

Udvid dine færdigheder
Gå på opdagelse i kurser
Få nye funktioner først
Deltag i Microsoft insiders

Var disse oplysninger nyttige?

Hvad påvirkede din oplevelse?

Tak for din feedback!

×