Skip to content

Commit a2a9ea1

Browse files
20241029 2350
1 parent 9433a13 commit a2a9ea1

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ ms.custom:
1919
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.
2020

2121
> [!NOTE]
22-
> 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/ordered-columnstore-indexes).
22+
> 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).
2323
2424
## Ordered vs. non-ordered clustered columnstore index
2525

0 commit comments

Comments
 (0)