Merge pull request #212752 from WilliamDAssafMSFT/patch-3

Update design-guidance-for-replicated-tables.md

Author: prmerger-automator[bot]

articles/synapse-analytics/sql-data-warehouse/design-guidance-for-replicated-tables.md

@@ -5,7 +5,7 @@ manager: craigg
 ms.service: synapse-analytics
 ms.topic: conceptual
 ms.subservice: sql-dw 
-ms.date: 11/02/2021
+ms.date: 09/27/2022
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: 
@@ -47,6 +47,9 @@ Replicated tables may not yield the best query performance when:
 - The SQL pool is scaled frequently. Scaling a SQL pool changes the number of Compute nodes, which incurs rebuilding the replicated table.
 - The table has a large number of columns, but data operations typically access only a small number of columns. In this scenario, instead of replicating the entire table, it might be more effective to distribute the table, and then create an index on the frequently accessed columns. When a query requires data movement, SQL pool only moves data for the requested columns.
 
+> [!TIP]
+> For more guidance on indexing and replicated tables, see the [Cheat sheet for dedicated SQL pool (formerly SQL DW) in Azure Synapse Analytics](cheat-sheet.md#index-your-table).
+
 ## Use replicated tables with simple query predicates
 
 Before you choose to distribute or replicate a table, think about the types of queries you plan to run against the table. Whenever possible,