Skip to content

Commit 905dea5

Browse files
Merge pull request #209062 from rdeltcheva/ase-minor
Minor clarification about saptune/RHEL versions
2 parents a9231a5 + 695bf9b commit 905dea5

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

articles/virtual-machines/workloads/sap/dbms_guide_sapase.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -7,11 +7,11 @@ tags: azure-resource-manager
77
ms.service: virtual-machines-sap
88
ms.topic: article
99
ms.workload: infrastructure
10-
ms.date: 08/24/2022
10+
ms.date: 08/23/2022
1111
ms.author: juergent
1212
ms.custom: H1Hack27Feb2017
13-
---
1413

14+
---
1515
# SAP ASE Azure Virtual Machines DBMS deployment for SAP workload
1616

1717
In this document, covers several different areas to consider when deploying SAP ASE in Azure IaaS. As a precondition to this document, you should have read the document [Considerations for Azure Virtual Machines DBMS deployment for SAP workload](dbms_guide_general.md) and other guides in the [SAP workload on Azure documentation](./get-started.md). This document covers SAP ASE running on Linux and on Windows Operating Systems. The minimum supported release on Azure is SAP ASE 16.0.02 (Release 16 Support Pack 2). It is recommended to deploy the latest version of SAP and the latest Patch Level. As a minimum SAP ASE 16.0.03.07 (Release 16 Support Pack 3 Patch Level 7) is recommended. The most recent version of SAP can be found in [Targeted ASE 16.0 Release Schedule and CR list Information](https://wiki.scn.sap.com/wiki/display/SYBASE/Targeted+ASE+16.0+Release+Schedule+and+CR+list+Information).
@@ -26,7 +26,7 @@ Additional information about release support with SAP applications or installati
2626
Remark: Throughout documentation within and outside the SAP world, the name of the product is referenced as Sybase ASE or SAP ASE or in some cases both. In order to stay consistent, we use the name **SAP ASE** in this documentation.
2727

2828
## Operating system support
29-
The SAP Product Availability Matrix contains the supported Operating System and SAP Kernel combinations for each SAP application. Linux distributions SUSE 12.x, SUSE 15.x, Red Hat 7.x are fully supported. Oracle Linux as operating system for SAP ASE is not supported. It is recommended to use the most recent Linux releases available. Windows customers should use Windows Server 2016 or Windows Server 2019 releases. Older releases of Windows such as Windows 2012 are technically supported but the latest Windows version is always recommended.
29+
The SAP Product Availability Matrix contains the supported Operating System and SAP Kernel combinations for each SAP application. Linux distributions SLES 12.x, SLES 15.x, RHEL 7.x and RHEL 8.x are fully supported. Oracle Linux as operating system for SAP ASE is not supported. It is recommended to use the most recent Linux releases available. Windows customers should use Windows Server 2016 or Windows Server 2019 releases. Older releases of Windows such as Windows 2012 are technically supported but the latest Windows version is always recommended.
3030

3131

3232
## Specifics to SAP ASE on Windows
@@ -40,7 +40,7 @@ Lock Pages in Memory is a setting that will prevent the SAP ASE database buffer
4040

4141

4242
## Linux operating system specific settings
43-
On Linux VMs, run `saptune` with profile SAP-ASE
43+
On SLES VMs, run `saptune` with profile SAP-ASE. Tune RHEL VMs as described in [69988](https://access.redhat.com/solutions/69988).
4444
Linux Huge Pages should be enabled by default and can be verified with command
4545

4646
`cat /proc/meminfo`
@@ -81,7 +81,7 @@ An example of a configuration for a small SAP ASE DB Server with a database size
8181
| # of data devices | 4 | 4 | ---|
8282
| # of log devices | 1 | 1 | --- |
8383
| # of temp devices | 1 | 1 | More for SAP BW workload |
84-
| Operating system | Windows Server 2019 | SUSE 12 SP4/ 15 SP1 or RHEL 7.6 | --- |
84+
| Operating system | Windows Server 2019 | SLES 12 SP4/ 15 SP1 or RHEL 7.6/8.1 | --- |
8585
| Disk aggregation | Storage Spaces | LVM2 | --- |
8686
| File system | NTFS | XFS |
8787
| Format block size | Needs workload testing | Needs workload testing | --- |
@@ -102,7 +102,7 @@ An example of a configuration for a medium SAP ASE DB Server with a database siz
102102
| # of data devices | 8 | 8 | ---|
103103
| # of log devices | 1 | 1 | --- |
104104
| # of temp devices | 1 | 1 | More for SAP BW workload |
105-
| Operating system | Windows Server 2019 | SUSE 12 SP4/ 15 SP1 or RHEL 7.6 | --- |
105+
| Operating system | Windows Server 2019 | SLES 12 SP4/ 15 SP1 or RHEL 7.6/8.1 | --- |
106106
| Disk aggregation | Storage Spaces | LVM2 | --- |
107107
| File system | NTFS | XFS |
108108
| Format block size | Needs workload testing | Needs workload testing | --- |
@@ -122,7 +122,7 @@ An example of a configuration for a small SAP ASE DB Server with a database size
122122
| # of data devices | 16 | 16 | ---|
123123
| # of log devices | 1 | 1 | --- |
124124
| # of temp devices | 1 | 1 | More for SAP BW workload |
125-
| Operating system | Windows Server 2019 | SUSE 12 SP4/ 15 SP1 or RHEL 7.6 | --- |
125+
| Operating system | Windows Server 2019 | SLES 12 SP4/ 15 SP1 or RHEL 7.6/8.1 | --- |
126126
| Disk aggregation | Storage Spaces | LVM2 | --- |
127127
| File system | NTFS | XFS |
128128
| Format block size | Needs workload testing | Needs workload testing | --- |
@@ -143,7 +143,7 @@ An example of a configuration for a small SAP ASE DB Server with a database size
143143
| # of data devices | 32 | 32 | ---|
144144
| # of log devices | 1 | 1 | --- |
145145
| # of temp devices | 1 | 1 | More for SAP BW workload |
146-
| Operating system | Windows Server 2019 | SUSE 12 SP4/ 15 SP1 or RHEL 7.6 | --- |
146+
| Operating system | Windows Server 2019 | SLES 12 SP4/ 15 SP1 or RHEL 7.6/8.1 | --- |
147147
| Disk aggregation | Storage Spaces | LVM2 | --- |
148148
| File system | NTFS | XFS |
149149
| Format block size | Needs workload testing | Needs workload testing | --- |
@@ -210,13 +210,13 @@ SAP Software provisioning Manager (SWPM) is giving an option to encrypt the data
210210

211211
- Deploy SAP ASE 16.0.03.07 or higher
212212
- Update to latest version and patches of FaultManager and SAPHostAgent
213-
- Deploy on latest certified OS available such as Windows 2019, Suse 15.1 or Redhat 7.6 or higher
213+
- Deploy on latest certified OS available such as Windows 2019, SLES 15 or RHEL 8
214214
- Use SAP Certified VMs – high memory Azure VM SKUs such as Es_v3 or for x-large systems M-Series VM SKUs are recommended
215215
- Match the disk IOPS and total VM aggregate throughput quota of the VM with the disk design. Deploy sufficient number of disks
216216
- Aggregate disks using Windows Storage Spaces or Linux LVM2 with correct stripe size and file system
217217
- Create sufficient number of devices for data, log, temp, and backup purposes
218218
- Consider using UltraDisk for x-large systems
219-
- Run `saptune` SAP-ASE on Linux OS
219+
- Run `saptune` SAP-ASE on SLES. Tune RHEL VMs per [69988](https://access.redhat.com/solutions/69988).
220220
- Secure the database with DB Encryption – manually store keys in Azure Key Vault
221221
- Complete the [SAP on Azure Checklist](./sap-deployment-checklist.md)
222222
- Configure log backup and full backup

0 commit comments

Comments
 (0)