Troubleshooting SQL Server 2014 Bulk Copy Problems
If you have problems with SQL Server 2014 bulk copy, review this troubleshooting checklist
to find potential solutions.
1. Install the latest SQL Server 2014 service pack.
Because many SQL Server 2014 bulk copy bugs were fixed in SQL Server service packs,
you should install the latest SQL Server service pack.
At the time this article was written the latest SQL Server 2014 service pack was service
pack 1. You can download the SQL Server 2014 service pack 1 at here:
https://www.microsoft.com/en-us/download/details.aspx?id=46694
2. The error 674 may occur during the bulk insert operations.
This error indicates a problem related to releasing pre-allocated disk blocks used during
bulk-insert operations. To resolve this problem, you should restart the server.
3. The error 4803 occurs during the bulk copy operation.
This is the error message text: “The bulk copy (bcp) client has sent a row length of %d.
This is not a valid size. The maximum row size is %d.” To work around this problem, you
should Use a supported client application programming interface (API).
4. The error 4868 occurs when you bulk load data into table.
This is the error message text: “The bulk load failed. The codepage “%d” is not installed.”
To resolve this problem, you should Install the codepage and run the command again.
5. The error 4876 may occur during the Bulk Insert operation.
This is the error message text: “The Bulk Insert operation of SQL Server Destination has
timed out.” To resolve this problem, you can increase the value of Timeout property on the
SQL Server Destination in the dataflow.
6. The error 5301 occurs when you bulk load data into table.
This error indicates that bulk load fails because user does not have the ALTER TABLE
permission on the target table of a bulk load. This problem occurs when the target
table contains triggers or check constraints. To work around this problem, you should
grant the ALTER TABLE permission for the user.
7. The error occurs when you run a “BULK INSERT” query on a database that uses the
“BULK_LOGGED” or “SIMPLE” recovery model in SQL Server 2014.
This problem occurs when you turn on the SET XACT_ABORT switch. This bug was first
fixed in Cumulative Update package 1 for SQL Server 2014. You can download the
Cumulative Update package 1 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/2931693
To work around this problem, you can set the database to the “Full” recovery model.
8. Poor performance when you bulk insert into partitioned cluster columnstore index (CCI).
This is SQL Server 2014 bug. This bug was first fixed in Cumulative Update package 2
for SQL Server 2014. You can download the Cumulative Update package 2 for
SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/2967546
9. When you try to run bulk copy (BCP) on the partitioned table that has a
clustered columnstore index, BCP fails.
This problem occurs when the table contains the char, nchar, varchar, nvarchar, or
varbinary data type. This bug was first fixed in Cumulative Update package 3 for
SQL Server 2014. You can download the Cumulative Update package 3 for SQL Server 2014
at here:
https://support.microsoft.com/en-us/kb/2984923
10. When you use the bcp_init function in SQL Server Native Client 11.0 to do bulk
copy, and set a local temp table as the input parameter, the function fails.
This is SQL Server 2014 bug. This bug was first fixed in Cumulative Update package 4
for SQL Server 2014. You can download the Cumulative Update package 4 for
SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/2999197
To work around this problem, avoid using a local temp table as the input parameter
for the bcp_init function.
11. The error occurs when you do bulk copy on double-byte character set (DBCS)
by using ODBC Driver 11 in SQL Server 2014.
This is the error message text: “String data, right truncation”. This bug was first
fixed in Cumulative Update package 4 for SQL Server 2014. You can download the
Cumulative Update package 4 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/2999197
12. You may receive an error message when you run a query that contains INSERT
statements if trace flags 4199 and 610 are enabled.
This is the error message text: “Cannot bulk load”. This bug was first fixed in
Cumulative Update package 7 for SQL Server 2014. You can download the Cumulative
Update package 7 for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/3046038
13. The error 3624 occurs when you execute a query that contains multiple
bulk insert statements.
This is SQL Server 2014 bug. This bug was first fixed in Cumulative Update
package 7 for SQL Server 2014. You can download the Cumulative Update package 7
for SQL Server 2014 at here:
https://support.microsoft.com/en-us/kb/3046038