Merge pull request #289460 from WilliamDAssafMSFT/20241023-ordered-columnstore

20241029 1454

Author: prmerger-automator[bot]

articles/synapse-analytics/sql-data-warehouse/performance-tuning-ordered-cci.md

@@ -12,12 +12,15 @@ ms.custom:
   - azure-synapse
 ---
 
-# Performance tuning with ordered clustered columnstore index
+# Performance tuning with ordered clustered columnstore index in Azure Synapse Analytics
 
-**Applies to:** Azure Synapse Analytics dedicated SQL pools, SQL Server 2022 (16.x) and later
+**Applies to:** Azure Synapse Analytics dedicated SQL pools
 
 When users query a columnstore table in dedicated SQL pool, the optimizer checks the minimum and maximum values stored in each segment. Segments that are outside the bounds of the query predicate aren't read from disk to memory. A query can finish faster if the number of segments to read and their total size are small.
 
+> [!NOTE]
+> This article applies to Azure Synapse Analytics dedicated SQL pools. For information on ordered columnstore indexes in SQL Server and other SQL platforms, see [Performance tuning with ordered clustered columnstore indexes](/sql/relational-databases/indexes/columnstore-indexes-overview#ordered-columnstore-indexes).
+
 ## Ordered vs. non-ordered clustered columnstore index
 
 By default, for each table created without an index option, an internal component (index builder) creates a non-ordered clustered columnstore index (CCI) on it.  Data in each column is compressed into a separate CCI rowgroup segment.  There's metadata on each segment's value range, so segments that are outside the bounds of the query predicate aren't read from disk during query execution.  CCI offers the highest level of data compression and reduces the size of segments to read so queries can run faster. However, because the index builder doesn't sort data before compressing them into segments, segments with overlapping value ranges could occur, causing queries to read more segments from disk and take longer to finish.