You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/sap/workloads/planning-guide-storage.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -261,7 +261,7 @@ For information about service levels, see [Service levels for Azure NetApp Files
261
261
- SAPMNT share: Performance, ideally Ultra
262
262
- Global transport directory: Performance, ideally Ultra
263
263
264
-
Sizing recommendations are available in the [SAP on Azure NetApp FIles TCO Estimator](https://aka.ms/anfsapcalc).
264
+
Sizing recommendations are available in the [SAP on Azure NetApp Files TCO Estimator](https://aka.ms/anfsapcalc).
265
265
266
266
> [!NOTE]
267
267
> The minimum provisioning size is a 1 TiB unit that is called capacity pool. You then create volumes out of this capacity pool. Whereas the smallest volume you can build is 100 GiB. You can expand a capacity pool in 1 TiB see. For pricing, see [Azure NetApp Files Pricing](https://azure.microsoft.com/pricing/details/netapp/)
@@ -281,7 +281,7 @@ Azure NetApp Files is currently supported for several SAP workload scenarios:
281
281
> [!NOTE]
282
282
> So far no DBMS workloads are supported on SMB based on Azure NetApp Files.
283
283
284
-
Storage for database applications typically has throughput requirements that do not scale linearly with the size of the volumes, ie log volumes are relatively small in size but require high levels of throughput.
284
+
Storage for database applications typically has throughput requirements that don't scale linearly with the size of the volumes, ie log volumes are relatively small in size but require high levels of throughput.
285
285
286
286
Azure NetApp Files allows you to allocate volume throughput independently from volume sizes when using a capacity pool of type [manual QoS](../../azure-netapp-files/azure-netapp-files-service-levels.md#throughput-limit-examples-of-volumes-in-a-manual-qos-capacity-pool).
287
287
@@ -310,7 +310,7 @@ The capability matrix for SAP workload looks like:
310
310
| Latency | Very low | Typically less than 1 ms |
311
311
| IOPS SLA | Yes | - |
312
312
| IOPS linear to capacity | Linear with auto QoS; independent with Manual QoS | Three [service levels](../../azure-netapp-files/azure-netapp-files-service-levels.md) available |
313
-
| Throughput SLA | Yes | - |
313
+
| Throughput SLA | Yes | - |Sizing recommendations are available in the SAP on Azure NetApp FIles TCO Esti
314
314
| Throughput linear to capacity | Linear with auto QoS; independent with Manual QoS | Three [service levels](../../azure-netapp-files/azure-netapp-files-service-levels.md) available |
0 commit comments