SQL Server Database, Datafile, Filegroup Compression

Running a Smaller Database Footprint

HyperBac Online is designed with the same principles as HyperBac for SQL Server. The main difference between both products is that HyperBac Online enables you to run your live database as a compressed entity. This, in respect to SQL Server, means that your .mdf, .ldf and .ndf files occupy less than 20% of their native file size. This brings a significant reduction in your storage footprint.

Consider the example where a database is created with an initial size of 1TB. This would natively occupy 1TB on the file system, irrespective of how much data is actually in the database.

Now let’s also assume that that database has 800GB of actual data and the remaining 200GB is free or unallocated space.

If we run this database as a compressed database (at 80%) HyperBac Online volume, then that 1TB becomes 160GB. We achieve 84% compression because the white space compresses to zero and the used space compresses by 80% to 160GB.

With HyperBac Online, we compress the footprint of the actual database itself.

Why does this matter?

Using HyperBac Online for each of the following example scenarios means that HyperBac frees up resources typically consumed by non-production systems. HyperBac Online can help to accomplish the following:

1.   Reduce the footprint of the multitude of development and QA databases that are constantly being refreshed from production

2.   Reduce the footprint of reporting databases

This reduction both in storage and application footprint means HyperBac Online gives storage and bandwidth resources back, which you can use for more mission-critical systems.