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
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 2016
Latest cumulative update for SQL Server 2012 SP3
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.