Skip to content

Commit fd9946a

Browse files
Update memory-concurrency-limits.md
Minor changes
1 parent 73f5e14 commit fd9946a

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/synapse-analytics/sql-data-warehouse/memory-concurrency-limits.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ The service levels range from DW100c to DW30000c.
5050
The maximum service level is DW30000c, which has 60 Compute nodes and one distribution per Compute node. For example, a 600 TB data warehouse at DW30000c processes approximately 10 TB per Compute node.
5151

5252
> [!NOTE]
53-
> Synapse Dedicated SQL pool is an evergreen platform service. Under [shared responsibility model in the cloud](https://learn.microsoft.com/azure/security/fundamentals/shared-responsibility#division-of-responsibility), Microsoft continues to invest in advancements to underlying software and hardware which host dedicated SQL pool. As a result, the number of nodes or the type of computer hardware which underpins a given performance level (SLO) may change. The number of compute nodes listed here are provided as a reference, and shouldn't be used for sizing or performance purposes. Irrespective of number of nodes or underlying infrastructure, Microsoft's goal is to deliver performance in accordance with provisioned SLO (or DWUs); hence, we recommend that all sizing exercises must use DWU as a guide.
53+
> Synapse Dedicated SQL pool is an evergreen platform service. Under [shared responsibility model in the cloud](https://learn.microsoft.com/azure/security/fundamentals/shared-responsibility#division-of-responsibility), Microsoft continues to invest in advancements to underlying software and hardware which host dedicated SQL pool. As a result, the number of nodes or the type of computer hardware which underpins a given performance level (SLO) may change. The number of compute nodes listed here are provided as a reference, and shouldn't be used for sizing or performance purposes. Irrespective of number of nodes or underlying infrastructure, Microsoft's goal is to deliver performance in accordance with SLO; hence, we recommend that all sizing exercises must use cDWU as a guide. For more information on SLO and compute Data Warehouse Units, please refer to link [here](https://learn.microsoft.com/azure/synapse-analytics/sql-data-warehouse/what-is-a-data-warehouse-unit-dwu-cdwu#service-level-objective).
5454
5555
## Concurrency maximums for workload groups
5656

0 commit comments

Comments
 (0)