Skip to content

Commit f1fd57b

Browse files
msjuergentmsjuergent
committed
update examples
1 parent 5300e86 commit f1fd57b

File tree

1 file changed

+34
-31
lines changed

1 file changed

+34
-31
lines changed

‎articles/sap/workloads/dbms-guide-ibm.md

Lines changed: 34 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ keywords: 'Azure, Db2, SAP, IBM'
77
ms.service: sap-on-azure
88
ms.subservice: sap-vm-workloads
99
ms.topic: article
10-
ms.date: 03/07/2024
10+
ms.date: 08/29/2024
1111
ms.author: juergent
1212
ms.custom: H1Hack27Feb2017, linux-related-content
1313
---
@@ -87,52 +87,55 @@ On Windows using Storage pools for Db2 storage paths for `log_dir`, `sapdata` an
8787

8888
IBM Db2 for SAP NetWeaver Applications is supported on any VM type listed in SAP support note [1928533]. Recommended VM families for running IBM Db2 database are Esd_v4/Eas_v4/Es_v3 and M/M_v2-series for large multi-terabyte databases. The IBM Db2 transaction log disk write performance can be improved by enabling the M-series Write Accelerator.
8989

90-
Following is a baseline configuration for various sizes and uses of SAP on Db2 deployments from small to large. The list is based on Azure premium storage. However, Azure Ultra disk is fully supported with Db2 as well and can be used as well. Use the values for capacity, burst throughput, and burst IOPS to define the Ultra disk configuration. You can limit the IOPS for the /db2/```<SID>```/log_dir at around 5000 IOPS.
90+
Following is a baseline configuration for various sizes and uses of SAP on Db2 deployments from small to x-large.
91+
92+
>[!IMPORTANT]
93+
> The VM types listed below are examples that meet the vCPU and memory critiera of each of the categories. The storage configuration is based on Azure premium storage v1. Premium SSD v2 and Azure Ultra disk is fully supported with IBM Db2 as well and can be used for deployments. Use the values for capacity, burst throughput, and burst IOPS to define the Ultra disk or Premium SSD v2 configuration. You can limit the IOPS for the /db2/```<SID>```/log_dir at around 5000 IOPS. Adjust the throughput and IOPS to the specific workload if these baseline discussions don't meet the requirements
9194
9295
#### Extra small SAP system: database size 50 - 200 GB: example Solution Manager
93-
| 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 |
96+
| VM Size / Examples |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 |
9497
| --- | --- | --- | :---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: |
95-
|E4ds_v4 |/db2 |P6 |1 |240 |50 |64 |3,500 |170 || |
96-
|vCPU: 4 |/db2/```<SID>```/sapdata |P10 |2 |1,000 |200 |256 |7,000 |340 |256<br />KB |ReadOnly |
97-
|RAM: 32 GiB |/db2/```<SID>```/saptmp |P6 |1 |240 |50 |128 |3,500 |170 | ||
98-
| |/db2/```<SID>```/log_dir |P6 |2 |480 |100 |128 |7,000 |340 |64<br />KB ||
99-
| |/db2/```<SID>```/offline_log_dir |P10 |1 |500 |100 |128 |3,500 |170 || |
98+
| vCPU: 4 |/db2 |P6 |1 |240 |50 |64 |3,500 |170 || |
99+
| RAM: ~32 GiB |/db2/```<SID>```/sapdata |P10 |2 |1,000 |200 |256 |7,000 |340 |256<br />KB |ReadOnly |
100+
| E4(d)s_v5|/db2/```<SID>```/saptmp |P6 |1 |240 |50 |128 |3,500 |170 | ||
101+
| E4(d)as_v5 |/db2/```<SID>```/log_dir |P6 |2 |480 |100 |128 |7,000 |340 |64<br />KB ||
102+
| ... |/db2/```<SID>```/offline_log_dir |P10 |1 |500 |100 |128 |3,500 |170 || |
100103

101104
#### Small SAP system: database size 200 - 750 GB: small Business Suite
102-
| 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 |
105+
| VM Size / Examples |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 |
103106
| --- | --- | --- | :---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: |
104-
|E16ds_v4 |/db2 |P6 |1 |240 |50 |64 |3,500 |170 || |
105-
|vCPU: 16 |/db2/```<SID>```/sapdata |P15 |4 |4,400 |500 |1.024 |14,000 |680 |256 KB |ReadOnly |
106-
|RAM: 128 GiB |/db2/```<SID>```/saptmp |P6 |2 |480 |100 |128 |7,000 |340 |128 KB ||
107-
| |/db2/```<SID>```/log_dir |P15 |2 |2,200 |250 |512 |7,000 |340 |64<br />KB ||
108-
| |/db2/```<SID>```/offline_log_dir |P10 |1 |500 |100 |128 |3,500 |170 |||
107+
| vCPU: 16 |/db2 |P6 |1 |240 |50 |64 |3,500 |170 || |
108+
| RAM: ~128 GiB |/db2/```<SID>```/sapdata |P15 |4 |4,400 |500 |1.024 |14,000 |680 |256 KB |ReadOnly |
109+
| E16(d)s_v5 |/db2/```<SID>```/saptmp |P6 |2 |480 |100 |128 |7,000 |340 |128 KB ||
110+
| E16(d)as_v5 |/db2/```<SID>```/log_dir |P15 |2 |2,200 |250 |512 |7,000 |340 |64<br />KB ||
111+
| ... |/db2/```<SID>```/offline_log_dir |P10 |1 |500 |100 |128 |3,500 |170 |||
109112

110113
#### Medium SAP system: database size 500 - 1000 GB: small Business Suite
111-
| 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 |
114+
| VM Size / Examples |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 |
112115
| --- | --- | --- | :---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: |
113-
|E32ds_v4 |/db2 |P6 |1 |240 |50 |64 |3,500 |170 || |
114-
|vCPU: 32 |/db2/```<SID>```/sapdata |P30 |2 |10,000 |400 |2.048 |10,000 |400 |256 KB |ReadOnly |
115-
|RAM: 256 GiB |/db2/```<SID>```/saptmp |P10 |2 |1,000 |200 |256 |7,000 |340 |128 KB ||
116-
| |/db2/```<SID>```/log_dir |P20 |2 |4,600 |300 |1.024 |7,000 |340 |64<br />KB ||
117-
| |/db2/```<SID>```/offline_log_dir |P15 |1 |1,100 |125 |256 |3,500 |170 |||
116+
| vCPU: 32 |/db2 |P6 |1 |240 |50 |64 |3,500 |170 || |
117+
| RAM: ~256 GiB |/db2/```<SID>```/sapdata |P30 |2 |10,000 |400 |2.048 |10,000 |400 |256 KB |ReadOnly |
118+
| E32(d)s_v5 |/db2/```<SID>```/saptmp |P10 |2 |1,000 |200 |256 |7,000 |340 |128 KB ||
119+
| E32(d)as_v5 |/db2/```<SID>```/log_dir |P20 |2 |4,600 |300 |1.024 |7,000 |340 |64<br />KB ||
120+
| M32ls |/db2/```<SID>```/offline_log_dir |P15 |1 |1,100 |125 |256 |3,500 |170 |||
118121

119122
#### Large SAP system: database size 750 - 2000 GB: Business Suite
120-
| 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 |
123+
| VM Size / Examples |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 |
121124
| --- | --- | --- | :---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: |
122-
|E64ds_v4 |/db2 |P6 |1 |240 |50 |64 |3,500 |170 || |
123-
|vCPU: 64 |/db2/```<SID>```/sapdata |P30 |4 |20,000 |800 |4.096 |20,000 |800 |256 KB |ReadOnly |
124-
|RAM: 504 GiB |/db2/```<SID>```/saptmp |P15 |2 |2,200 |250 |512 |7,000 |340 |128 KB ||
125-
| |/db2/```<SID>```/log_dir |P20 |4 |9,200 |600 |2.048 |14,000 |680 |64<br />KB ||
126-
| |/db2/```<SID>```/offline_log_dir |P20 |1 |2,300 |150 |512 |3,500 |170 || |
125+
| vCPU: 64 |/db2 |P6 |1 |240 |50 |64 |3,500 |170 || |
126+
| RAM: ~512 GiB |/db2/```<SID>```/sapdata |P30 |4 |20,000 |800 |4.096 |20,000 |800 |256 KB |ReadOnly |
127+
| E64(d)s_v5 |/db2/```<SID>```/saptmp |P15 |2 |2,200 |250 |512 |7,000 |340 |128 KB ||
128+
| E64(d)as_v5 |/db2/```<SID>```/log_dir |P20 |4 |9,200 |600 |2.048 |14,000 |680 |64<br />KB ||
129+
| M64ls |/db2/```<SID>```/offline_log_dir |P20 |1 |2,300 |150 |512 |3,500 |170 || |
127130

128131
#### Large multi-terabyte SAP system: database size 2 TB+: Global Business Suite system
129132
| 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 |
130133
| --- | --- | --- | :---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: |
131-
|M128s |/db2 |P10 |1 |500 |100 |128 |3,500 |170 || |
132-
|vCPU: 128 |/db2/```<SID>```/sapdata |P40 |4 |30,000 |1.000 |8.192 |30,000 |1.000 |256 KB |ReadOnly |
133-
|RAM: 2,048 GiB |/db2/```<SID>```/saptmp |P20 |2 |4,600 |300 |1.024 |7,000 |340 |128 KB ||
134-
| |/db2/```<SID>```/log_dir |P30 |4 |20,000 |800 |4.096 |20,000 |800 |64<br />KB |Write-<br />Accelerator |
135-
| |/db2/```<SID>```/offline_log_dir |P30 |1 |5,000 |200 |1.024 |5,000 |200 || |
134+
| vCPU: =>128 |/db2 |P10 |1 |500 |100 |128 |3,500 |170 || |
135+
| RAM: =>2,048 GiB |/db2/```<SID>```/sapdata |P40 |4 |30,000 |1.000 |8.192 |30,000 |1.000 |256 KB |ReadOnly |
136+
| M128s_v2 |/db2/```<SID>```/saptmp |P20 |2 |4,600 |300 |1.024 |7,000 |340 |128 KB ||
137+
| M176s_2_v3 |/db2/```<SID>```/log_dir |P30 |4 |20,000 |800 |4.096 |20,000 |800 |64<br />KB |Write-<br />Accelerator |
138+
| M176s_3_v3,<br />M176s_4_v3 |/db2/```<SID>```/offline_log_dir |P30 |1 |5,000 |200 |1.024 |5,000 |200 || |
136139

137140

138141
### Using Azure NetApp Files

0 commit comments

Comments
 (0)