In solidDB, you can enable data compression in the database to save disk capacity, memory capacity, and disk I/O. Compression is not automatically turned on since it might have some undesirable side effects or, for example, cause problems with data that is already compressed.

The key reasons for compressing data in databases are related to reducing disk space and memory requirements or being able to process higher logical data volumes in the same capacity. As a side impact, disk I/O is also reduced due to processing compressed blocks instead of uncompressed blocks. All these benefits are applicable in solidDB.

In solidDB compression, only disk-based tables can be compressed. Both data tables and indexes are compressed. The storage for BLOBs is not compressed even if the BLOBs are referred from disk-based system tables. The BLOB directory in system tables can be compressed but the actual BLOB content cannot be compressed. Internal memory data (for example, memory used for cursors, or user statements) is not compressed, but due to processing compressed pages in memory, more data fits in the cache or less memory is required for a similar cache hit rate.

Transaction log files are not compressed. The disk capacity benefits are related to database files only.

solidDB compression works with all solidDB replication mechanisms (CREP, HotStandby, and Advanced Replication). Also, all linking models (client/server, LLA and SMA) are supported as are all client drivers.