ReaHat provides a similar tool, SQLStorageCompress, and claims to be able to achieve a compression ratio of 90%. SQLStorageCompress provides a 14-day version. After the version is downloaded, HyperBacControlService is started. This Service works with WindowsIOManager to compress or decompress SQL Server's read/write requests.
Rea Hat provides a similar tool, SQL Storage Compress, and claims to be able to achieve a compression ratio of 90%. SQL Storage Compress provides a 14-day version. After being downloaded, The HyperBac Control Service is started. This Service works with Windows I/O Manager to compress or decompress SQL Server's read/write requests.
Rea Hat provides a similar tool, SQL Storage Compress, and claims to be able to achieve a compression ratio of 90%. SQL Storage Compress provides a 14-day version. After being downloaded, The HyperBac Control Service is started. This service is used with Windows I/O Manager to compress or decompress SQL Server read/write requests, without affecting SQL Server users. For how it works, see:
SQLStorage Compress can Compress MDF, LDF, and NDF files, but only for files, not for single tables or individual indexes. Backup and restoration are the same as normal SQL Server operations. Compression and backup are not provided.
SQLStorage Compress provides a GUI that allows you to convert a database to a compressed database by restoring or restoring a database backup using a T-SQL. The following is a test I conducted, which is compressed by about 50%.
The operation interface is as follows:
After a data test, it took six minutes to insert 1000000 data and enable the compressed database. The database without enabling the compression did not end up running for six minutes, it may be that I/O is not good enough. I use SQL Server's built-in compression on the Server, which is slower than inserting data into tables that do not enable compression.