First, consider the T-SQL command that you would normally use to back up the "AdventureWorks" database:

BACKUP DATABASE [AdventureWorks] TO DISK = 'D:\Backups\AdventureWorks_backup.bak'

To back up AdventureWorks with SQL HyperBac standard compression:

In the T-SQL statement, simply change the extension of the backup file to .hbc:

BACKUP DATABASE [AdventureWorks] TO DISK = 'D:\Backups\AdventureWorks_backup.hbc'

That's all you need to do. SQL HyperBac will automatically apply compression to 'AdventureWorks_backup.hbc' when you run this T-SQL statement.

Whether you run the T-SQL statement from SQL Server Management Studio (either by explicitly typing the statement, or using the GUI options), using SQLCMD, or with any other tool, SQL HyperBac will automatically intercept the backup data, and compress it.

To back up AdventureWorks with SQL HyperBac fast compression:

In the T-SQL statement, simply change the extension of the backup file to .hbc2:

BACKUP DATABASE [AdventureWorks] TO DISK = 'D:\Backups\AdventureWorks_backup.hbc2'

To back up AdventureWorks with SQL HyperBac ZIP-compatible compression:

In the T-SQL statement, simply change the extension of the backup file to .zip or .rar:

BACKUP DATABASE [AdventureWorks] TO DISK = 'D:\Backups\AdventureWorks_backup.zip'

or,

BACKUP DATABASE [AdventureWorks] TO DISK = 'D:\Backups\AdventureWorks_backup.rar'

Exporting data from AdventureWorks.Sales.customer with SQL HyperBac standard compression

You can apply SQL HyperBac compression to the output of export operations (using 'bcp') in exactly the same way as for 'BACKUP DATABASE' commands.

Consider the bcp command that you would normally use to export data from the AdventureWorks.Sales.customer table (on a local instance named "PRODUCTION"):

bcp AdventureWorks.Sales.customer out D:\Backups\Export.dmp ‑Slocalhost\PRODUCTION ‑T ‑n ‑b1000

In the bcp command, simply change the extension of the export file to .hbc:

bcp AdventureWorks.Sales.customer out D:\Backups\Export.hbc ‑Slocalhost\PRODUCTION ‑T ‑n ‑b1000

Changing the .dmp extension to any of the other default extensions will cause SQL HyperBac to automatically process the export data as described.