Symptoms
Assume that you have a partitioned table that contains a computed partitioning column which is marked as PERSISTED in Microsoft SQL Server 2014 or 2016, and then you rebuild the partition online. In this situation, you receive the following error message:
Note
Msg 4819, Level 16, State 1, Line LineNumber
Cannot bulk load. The bulk data stream was incorrectly specified as sorted or the data violates a uniqueness constraint imposed by the target table. Sort order incorrect for the following two rows: primary key of first row: (RowNumber, DateTime), primary key of second row: (RowNumber, DateTime).
The statement has been terminated.
Resolution
To activate this hotfix, you have to enable the trace flag (TF) 176. This issue is fixed in the following cumulative updates for SQL Server:
Cumulative Update 7 for SQL Server 2016 SP1
Cumulative Update 4 for SQL Server 2016
Cumulative Update 6 for SQL Server 2014 SP2
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 2014
Workaround
To work around this issue, use SORT_IN_TEMPDB=ON in the rebuilding query.
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.