Skip to main content

Third Party Backup Tools – Redgate SQL Backup

To continue my little blog series on SQL Server backups, any series would not be complete without a look at some of the third party products that exist to supplement a backup plan with additional functionality not always offered in the native SQL Server backup.
My favourite tool and the backup product I have used the most over the years is Redgate’s SQL backup, there are other tools out there such as Hyperbac (Actually this has just been acquired by Redgate) and Litespeed, but over the years, for one reason or another I have used Redgate and have been very pleased with it.

Reasons for using Third Party Tools

“SQL ships with its own backup utility!” I hear you cry. “Why would you spend some extra $ on a third party tool when out of the box SQL Server can do this stuff for you?” Well I have a couple of reasons:
Compression – The main reason I started using Redgate backup way back on SQL Server 2000 was due to its ability to compress the backups it took. This remained true for SQL Server 2005 and with relatively large databases to look after for some clients with disk space at a relative premium and in some cases the need arose to keep three days worth of daily full backups on disk (backup were stored on tape too) for speed of recovery, this tool proved to be a real space saver.
Here’s an example:
This is a backup of the AdventureworksDW database on a SQL Server 2008 instance (More about SQL Server 2008 shortly) . The database is approximately 85MB
The native backup, with no compression looks like this:
BACKUP DATABASE [AdventureWorksDW2008] TO DISK =
N'C:\DATA\BackupComp\AW_Native_backup.bak' WITH NOFORMAT, NOINIT, NAME =
N'AdventureWorksDW2008-Full Database Backup', SKIP, NOREWIND, NOUNLOAD,

The Redgate (Redgate SQL backup needs to be installed on SQL instance for this script to work) script looks like this

EXECUTE master..sqlbackup
'-SQL "BACKUP DATABASE [AdventureWorksDW2008]
TO DISK = ''C:\DATA\BackupComp\AW_Redgate_Backup_Compressed.sqb''


As you can see even with this small databases the percentage disk space saving of the third party compressed backup can really save disk space with large databases.

SQL Server 2008 Enterprise Edition, SQL Server R2 Enterprise edition and Standard edition (new for SQL Server 2008 R2) include compression. This link gives details of the R2 compression with Standard edition.

How does the native encryption compare to the third party tool:

Here’s a native SQL Server 2008 backup with compression:

BACKUP DATABASE [AdventureWorksDW2008] TO DISK =
N'C:\DATA\BackupComp\AW_Native_Compressed.BAK' WITH NOFORMAT, INIT, NAME =
N'AdventureWorksDW2008-Full Database Backup', SKIP, NOREWIND, NOUNLOAD,

Here are the backup files and their respective sizes


As you can see the third party tool compression still outperforms the native compression in terms of disk space footprint.

Encryption – Native SQL backups are stored in plain text format, which means that the data stored in the backup in a text editor. so potentially someone with access to the file system, who shouldn’t have access to the database could potentially see the data. With Redgate SQL backup and other third party tools you can encrypt the backup so it cannot be read without being decrypted.

This article has highlighted some of the benefits of using third part tools and a full round up would not be complete without highlighting what I think is the main negative. You need to have the software installed on all the instances that you intend to restore too, so for example if you use the third party product to backup the production database on a production server if you want to take the third party generated backup file from production and restore to a test or dev environment to work with production data you need an extra license for the software on that environment. This can increase the cost slightly. That said Redgate, I can’t really speak for the other vendors, do provide a utility to convert their backup files to native SQL Server backup for restoring to severs without their software installed so although not completely straight forward it is possible to restore third party backup files to servers without the the third party tool installed.

Related Posts

Backup All Your Databases

Transaction Log Backups

Managing Your Backup Files

Differential Backups


  1. What kind of compression do you see when you have enabled TDE on the database?

  2. I've not tested it on TDE enabled 2008 DB yet Richard. Will look into it though and post back.


Post a Comment

Popular posts from this blog

SQL Server 2012 and Virtual Service Accounts

This post is written by David Postlethwaite
If you are using SQL Server 2012 you will probably have noticed that the default account for the SQL services has changed from that used in previous versions. With SQL 2005 and 2008 the default account for SQL service and SQL Agent service was “NT Authority\System”. This is one the built in accounts on a Windows machine, managed by the machine and selectable from a dedicated dropdown list

The Network Service account was introduced in Windows 2003 as an alternative to using the LocalSystem account, which has full local system privileges on the local machine, a major security concern.
The Network Service has limited local privileges easing these security concerns but when many services on a machine use the Network Service account it becomes harder to track which service is actually accessing resources and performing actions, because all the services are using the one Network Service account.
Also, this account, by default, has sysadmin per…

Always Encrypted

By David Postlethwaite

Always Encrypted is new features in SQL Server 2016 and it is also available in Azure SQL Database. Here you can encrypt columns in a table with a master key and a certificate so that they will appear as encrypted strings to those who don’t have the required certificate installed on their pc.
Once the certificate is installed on the computer then the unencrypted data can then be seen as normal.

The data passes from database to your application as the encrypted value, only the application with the correct certificate can unencrypt the data so it is secure across the wire. This will go some way to resolving the concern of people worried about putting their sensitive data on a shared server in the cloud such as Microsoft Azure and accessing the data across the Internet.

At the time of writing Always Encrypted is only supported with ADO.NET 4.6, JDBC 6.0 and ODBC 13.1 but expect other driver to become available.

The calling application (including SSMS) must also hav…

New in SQL Server 2017: Graph Databases

David has recorded and published a video of his presentation on SQL Server Graph Database. In his video which you can watch below, David provides an excellent introduction into SQL Server 2017 Graph Databases. In his presentation he looks at Tennis results at tournaments for  his favourite player "The Fed"  Rodger Federer.

David  shows how to set up graph database and work with them in SQL Server 2017.

Graph Database is not new. Other vendors have had graph database capabilities for some time so Microsoft are quite late to the market. In David presentation it appears that Microsoft have done a reasonable job of implementing some of the graph database features but he does point some of the limitations of the Microsoft product too and suggests that it is not ready for production yet but Microsoft seem serious about this feature.

Please watch the video and feel free to leave a comment or feedback - David is delivering a version of this talk on Graph databases in SQL Saturday Ka…