Clustered columnstore index results in clustered index being created first #264
Description
- SqlPackage or DacFx Version: 16.1.8089.0
- .NET Framework (Windows-only) or .NET Core: >Net Core
- Environment (local platform and source/target platforms): Any
Steps to Reproduce:
- create table with only a clustered columns store index
- deploy table
- table is created clustered index is added and after that the clustered columnstore index is added with drop_existing.
For an existing table where columnstore is being added its a real pain
Did this occur in prior versions? If not - which version(s) did it work in?
Was reported back in 2017, Steven Green checked at the time and confirmed thats the way the code has always worked, probably due to the initial implementation of column store. It was also reported on Connect if thats of any use.
https://connect.microsoft.com/SQLServer/feedback/details/3120614/ssdt-clustered-columnstore-rebuild-behaviour
SQLPackage