SQL Server 2016 lets you create additional nonclustered indexes on tables with clustered ColumnStore indexes. Here is how it works.
SQL SERVER – Basics ColumnStore FAQ – Part II
Part II of my ColumnStore FAQ: what to check when a ColumnStore index causes a performance regression, starting with whether the optimizer used it.
SQL SERVER – ColumnStore Frequently Asked Queries
ColumnStore frequently asked queries on troubleshooting performance: did the optimizer use the ColumnStore index, and if not, why? Trace flags, hints and more.
Interview Question of the Week #040 – Difference Between Unique Index vs Unique Constraint
Compare index vs unique constraint behavior, test filtered uniqueness and NULLs, inspect catalog flags, and remove each object correctly.
Interview Question of the Week #039 – What is Included Column Index in SQL Server 2005 and Onwards?
Build an included column index to cover SQL Server queries, compare plans and reads, and distinguish key limits from leaf-level payload.
Interview Question of the Week #021 – Difference Between Index Seek and Index Scan (Table Scan)
Read index seek and index scan plans accurately, test equality and ranges, and judge lookups and rows read instead of fixed percentages.
SQL SERVER – Mistake to Avoid: Duplicate and Overlapping Indexes – Notes from the Field #073
Indexes do not always improve performance. Kathi Kellenberger explains why duplicate and overlapping indexes are a mistake to avoid.