We couldn’t sign you in
Select the account you want to use.


Assume that you mark a computed column as PERSISTED in a partitioned table in Microsoft SQL Server 2014 and 2016. When you try to rebuild a single partition of an index online on the table, an error message that resembles the following might occur.

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: (001, 9999, ABC, 987654321, YWZ, 98765), primary key of second row: (001, 0001, CDE, 123456789, YWZ, 123456).


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

      Cumulative Update 4 for SQL Server 2017

      Cumulative Update 7 for SQL Server 2016 SP1

      Cumulative Update 9 for SQL Server 2014 SP2

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 2017

Latest cumulative update for SQL Server 2016

Latest cumulative update for SQL Server 2014


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


Learn about the terminologythat Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!