We’ll explore how to avoid this common pitfall & Focus the areas that matter for performance improvements. Avoid majoring in the minors.
The Columnstore Delta Store: Small Loads and Open Rowgroups
Inspect the columnstore delta store, distinguish rowgroup states, and choose load sizes or targeted compression after small loads.
Ordered Clustered Columnstore Index for Better Rowgroup Elimination
Build an ordered clustered columnstore on SaleDate, compare segment ranges and skipped segments, and review how later loads affect order.
One Default Row per Customer With a Filtered Unique Index
Two browser tabs, two default addresses. Here is how a filtered unique index keeps the rule in the database and how to switch defaults safely.
Aggregate Pushdown: Letting the Columnstore Scan Do the Summing
Verify aggregate pushdown in columnstore scans, inspect locally aggregated rows, and compare numeric aggregates with expressions.
Rowstore to Columnstore: Replace the Clustered Index
Rowstore to columnstore is a change of the clustered index, and one command works in only one case. This post builds two tables of 600,000 rows, shows the error from DROP_EXISTING on a primary key, and converts each table the working way. It compares the sizes before and after.
COMPRESSION_DELAY Option for Columnstore Indexes: Test It
The COMPRESSION_DELAY option keeps a closed delta rowgroup uncompressed for a number of minutes, so rows that change soon after they arrive are cheaper to modify. This post loads two demo tables, updates fresh rows in each, and shows the deleted rows that early compression leaves behind.