You are currently offline, waiting for your internet to reconnect

Behavior changes when you add uniqueidentifier columns in a clustered Columnstore Index in SQL Server 2016

Summary
This article describes an update that makes the following changes to the Columnstore Indexes feature in SQL Server 2016:
  • Improves the ability to add a non uniqueidentifier column in a clustered Columnstore Index by assigning the default value of NEWID() or NEWSEQUENTIALID() expressions to it.
  • Improves the ability to add a uniqueidentifier column in a clustered Columnstore Index by using an expression of NEWSEQUENTIALID() and NEWID().
  • Fixes an issue that when you add a new uniqueidentifier column in a clustered Columnstore Index, and the new column has a NOT NULL or DEFAULT constraint, NULL values are added to the existing rows.

More information
This update is included in the following cumulative update for SQL Server:


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:

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 Microsoft uses to describe software updates.
Properties

Article ID: 3173436 - Last Review: 07/25/2016 22:01:00 - Revision: 1.0

Microsoft SQL Server 2016 Developer, Microsoft SQL Server 2016 Enterprise, Microsoft SQL Server 2016 Standard

  • kbqfe kbfix kbexpertiseinter kbsurveynew KB3173436
Feedback
com/ms.js"> ml>com/ms.js"> .gif?DI=4050&did=1&t=">ng = 1; var varCustomerTracking = 1; var Route = "76500"; var Ctrl = ""; document.write(" lickTracking = 1; var varCustomerTracking = 1; var Route = "76500"; var Ctrl = ""; document.write("