A whole nonclustered columnstore index.

Since a columnstore table is stored as a clustered columnstore index, both approaches have the same results.

A whole columnstore table or a whole clustered columnstore index.

You can configure columnstore archival compression on the following database objects: Use columnstore archival compression to further reduce the data size for situations when you can afford extra time and CPU resources to store and retrieve the data. For partitioned tables and indexes, you can configure the compression option for each partition, and the various partitions of an object do not have to have the same compression setting.įor columnstore tables and indexes, all columnstore tables and indexes always use columnstore compression and this is not user configurable.A whole table that is stored as a clustered index.A whole table that is stored as a heap.

You can configure row and page compression on the following database objects: However, extra CPU resources are required on the database server to compress and decompress the data, while data is exchanged with the application. In addition to saving space, data compression can help improve performance of I/O intensive workloads because the data is stored in fewer pages and queries need to read fewer pages from disk. SQL Server, Azure SQL Database, and Azure SQL Managed Instance support row and page compression for rowstore tables and indexes, and support columnstore and columnstore archival compression for columnstore tables and indexes.įor rowstore tables and indexes, use the data compression feature to help reduce the size of the database. Applies to: SQL Server (all supported versions) Azure SQL Database Azure SQL Managed Instance

Just cause 3 recompress all