Applies ToSQL Server 2012 Developer SQL Server 2012 Enterprise SQL Server 2012 Enterprise Core SQL Server 2012 Standard 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

Symptoms

Consider the following scenario:

  • You perform a bulk copy operation in SQL Server.

  • The operation triggers a call to a common language runtime (CLR) function.

  • The CLR function executes a Transact-SQL statement that contains a TRY…CATCH construct.

In this scenario, SQL Server crashes and generates an access violation. Additionally, a dump file is generated in the SQL Server error log.

Resolution

This issue is fixed in the following cumulative updates of SQL Server:

Cumulative Update 2 for SQL Server 2016 SP1

Cumulative Update 4 for SQL Server 2016

Cumulative Update 5 for SQL Server 2012 Service Pack 3

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 terminology that Microsoft uses to describe software updates.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.