View a markdown version of this page

Best Practice 19.3 – Use compression, reorganization, and reclaim strategies - SAP Lens

Best Practice 19.3 – Use compression, reorganization, and reclaim strategies

All databases supported by SAP provide mechanisms for reclaiming space. These mechanisms should be part of regular maintenance activities to minimize cost increases associated with extending memory or EBS volumes.

Suggestion 19.3.1 – Use database compression

Compression is a default characteristic in SAP HANA. Use of compression in other databases might require additional licenses but should be explored for cost and performance benefits. The following notes provide a starting point for the various databases, but refer to SAP and database documentation for additional information.

Database SAP Documentation or SAP Notes
SAP HANA SAP Note: 2112604 - FAQ: SAP HANA Compression [Requires SAP Portal Access]
SAP ASE (Consult SAP or Vendor documentation for guidance)
IBM Db2 SAP Note: 1555903 - DB6: Supported IBM Db2 Database Features [Requires SAP Portal Access]
Oracle SAP Note: 1289494 - FAQ: Oracle compression [Requires SAP Portal Access]
Microsoft SQL Server SAP Note: 1488135 - Database compression for SQL Server [Requires SAP Portal Access]
SAP MaxDB (Consult SAP or Vendor documentation for guidance)

Suggestion 19.3.2 – Use database reorganizations and reclaim operations

Space which is unused within the database, due to organic use or targeted archive and cleanup activities, might require a reorganization or reclaim operation to realize the space savings. By reclaiming space regularly, you will reduce the overall growth and requirement for additional storage or memory. The following notes provide a starting point for the various databases, but refer to SAP and database documentation:

Database SAP Documentation or SAP Notes
SAP HANA SAP Note: 2499913 - How to shrink SAP HANA Data Volume size [Requires SAP Portal Access]
SAP ASE SAP Note: 2543407 - reorg rebuild with online - SAP ASE for Business Suite [Requires SAP Portal Access]
IBM Db2 SAP Note: 1942183 - DB6: When to consider a table or index reorganization [Requires SAP Portal Access]
Oracle SAP Note: 541538 - FAQ: Reorganization [Requires SAP Portal Access]
Microsoft SQL Server SAP Note: 1721843 - MSSQL: Post-steps after archiving, deleting or compression [Requires SAP Portal Access]
SAP MaxDB (Consult SAP or Vendor documentation for guidance)