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/dbms-guide-ibm.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
@@ -60,15 +60,15 @@ Remote shared volumes like the Azure services in the listed scenarios are suppor
60
60
61
61
* Hosting Linux guest OS based Db2 data and log files on NFS shares hosted on Azure NetApp Files is supported!
62
62
63
-
If you're using disks based on Azure Page BLOB Storage or Managed Disks, the statements made in [Considerations for Azure Virtual Machines DBMS deployment for SAP workload](dbms-guide-general.md) apply to deployments with the Db2 DBMS as well.
63
+
If you're using disks based on Azure Page BLOB Storage or Managed Disks, the statements made in [Considerations for Azure Virtual Machines DBMS deployment for SAP workload](dbms-guide-general.md) apply to deployments with the Db2 DBMS (Database Management System) as well.
64
64
65
65
As explained earlier in the general part of the document, quotas on IOPS throughput for Azure disks exist. The exact quotas are depending on the VM type used. A list of VM types with their quotas can be found [here (Linux)](/azure/virtual-machines/sizes) and [here (Windows)](/azure/virtual-machines/sizes).
66
66
67
67
As long as the current IOPS quota per disk is sufficient, it's possible to store all the database files on one single mounted disk. Whereas you always should separate the data files and transaction log files on different disks/VHDs.
68
68
69
69
For performance considerations, also refer to chapter 'Data Safety and Performance Considerations for Database Directories' in SAP installation guides.
70
70
71
-
Alternatively, you can use Windows Storage Pools, which are only available in Windows Server 2012 and higher as described [Considerations for Azure Virtual Machines DBMS deployment for SAP workload](dbms-guide-general.md). On Linux you can use LVM or mdadm to create one large logical device over multiple disks.
71
+
Alternatively, you can use Windows Storage Pools, which are only available in Windows Server 2012 and higher as described [Considerations for Azure Virtual Machines DBMS deployment for SAP workload](dbms-guide-general.md). On Linux, you can use LVM or mdadm to create one large logical device over multiple disks.
72
72
73
73
<!-- log_dir, sapdata and saptmp are terms in the SAP and DB2 world and now spelling errors -->
74
74
@@ -129,7 +129,7 @@ Following is a baseline configuration for various sizes and uses of SAP on Db2 d
#### Large multi-terabyte SAP system: database size 2 TB+: Global Business Suite system
132
-
Especially for such larger systems it is important to evaluate the infrastructure that the system is currently running on and the resource consiuption data of those systems to find the best match of Azure compute and storage infrastructure and configuration.
132
+
Especially for such larger systems it's important to evaluate the infrastructure that the system is currently running on and the resource consumption data of those systems to find the best match of Azure compute and storage infrastructure and configuration.
133
133
134
134
| VM Name / Size |Db2 mount point |Azure Premium Disk |# of Disks |IOPS |Through-<br />put [MB/s]|Size [GB]|Burst IOPS |Burst Through-<br />put [GB]| Stripe size | Caching |
0 commit comments