Skip to Content

SQL database compression - SAP best-practices

Hello experts,

I have a question about SAP best-practice for SQL database compression. I am putting together a compression project to go from NONE compression to PAGE compression for my existing ERP 6.0 system. The knowledge I have of SQL Server seems to conflict with SAP best-practice according to other consultants I have talked to...

The consultants pointed out in the documentation "Using SQL Server Database Compression with SAP NetWeaver", it says:

Page compression: is always performed on top of row compression

As such, they say I must 1. Compress my database using ROW compression. And then after that is complete, 2. Compress my database again using PAGE compression. Is that right??? If it is right, it doesn't make sense why SAP would recommend compressing that way?

Any advice would be greatly appreciated!

Thanks,
Nick Taff

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • May 01, 2017 at 06:01 PM

    Hi Nicholas,

    You can apply page compression direclty. No need to apply Row compression before.

    I have compressed dozens SAP databases from NONE to PAGE during many tests I've performed.

    Check out SAP KBA 1744217.

    Add comment
    10|10000 characters needed characters exceeded