SQL Server 2016 RTM Bulk Insert crash dumps when column data type cannot be determined - by Cody Konior

Status : 

 


6
0
Sign in
to vote
ID 2798212 Comments
Status Active Workarounds
Type Bug Repros 2
Opened 6/8/2016 4:54:13 AM
Access Restriction Public

Description

On SQL Server 2016 RTM when doing a Bulk Insert on columns where the data type cannot be determined, and where the number of rows exceeds a certain threshold (i.e. thousands), the bulk insert will fail with: 

Msg 7399, Level 16, State 1, Line 127
The OLE DB provider "BULK" for linked server "(null)" reported an error. The provider did not give any information about the error.
Msg 7330, Level 16, State 2, Line 127
Cannot fetch a row from OLE DB provider "BULK" for linked server "(null)".

And a crash dump is generated. If you insert 0 or a space between each delimeter the bulk insert will succeed. This behaviour generates crash dumps on three different SQL 2016 RTM servers including one fresh from scratch, while no crash dumps are generated on equivalent SQL 2012 servers (the bulk insert succeeds).
Sign in to post a comment.
Posted by Cody Konior on 8/15/2016 at 9:15 PM
I can confirm this is working in SQL 2016 RTM CU1.
Posted by Ben Whitman on 6/20/2016 at 12:30 AM
I found that this is only a problem on servers with newer processors which support AVX instructions, so it looks like this is related to some of the AVX-related optimisations they've done with bulk insert in SQL 2016. I've passed this on to MS Support in a case I have open with them currently.