A few tables / indexes aren't compressed - Go ahead and compress with MSSCOMPRESS?

[former_member197700]

se38 -> MSSCOMPRESS, I can see 30 tables that aren't compressed.  Some don't have the table compressed.  Some don't have the index(es) compressed, and some are missing compress on both (it says NONE,NONE).  99.9% of tables have PAGE compression for table and PAGE compression for Indexes and it only these 30 that are different.

Is there any reason I should not run msscompress to compress these tables?  I did it in a test system already and everything seems fine.  Are there certain tables that should be excluded on purpose?

SAP Version is Netweaver 7.4 / SQL Server 2014

[former_member197700 · Accepted solution]

I ran msscompress without too many issues.  The larger tables can make the database log fill up.  Some tables aren't eligible for the online mode and need to be done offline, but it is clear from the log if that happens.  The tool was reliable, helped with performance, and reclaimed a lot of space.  Yes, as the admin above replied, the sap_* tables are always created uncompressed.  They are small so you can either leave them alone or select them all compress them.  On my system, all sap_* tables were done in less than a minute.

[yakcinar]

Hello Clifton,

There is no restriction in the note

1488135 - Database compression for SQL Server

I also think that program checks the conditions and if there is inconsistency about it it stops.

I have a system with 7.0 and SQL Server 2008 R2 SP3. I compressed all tables except "sap_*" named ones that are not direclty related to SAP.

So you can run compression for all tables, indexes.

Regards,

Yuksel AKCINAR

[clas_hortien]

Hi,

the lowercase sap_* objects are all related to the SAP database monitor (DBACockpit). They can be compressed as well without harming the system or the monitor.

Best regards

   Clas Hortien