ApexSQL Restore: the backup restore performance numbers are in

ApexSQL Restore attaches a SQL backup much faster than SSMS. We’ve measured and compared application performance to show its advantages over the SSMS and the leading competitor. Performance is determined by three key parameters: time needed, resources used and disk space consumed when restoring backups

Testing system

Performance tests were conducted using Windows server 2012 Datacenter based on Intel® Core™ i7 3517 CPU 2.4GHz platform with a total of two processors. Software environment: ApexSQL Restore 2012 01, Microsoft SSMS 11.0, SQL 2012 and 2008 R2. Leading competitor: RedGate® SQL Virtual Restore 2.4 Three types of databases were used:

  • Large database 1,130 MB
  • Medium database 653 MB
  • Small database 209 MB

Each database includes all data types. While performing the tests, no additional sessions or applications were running, therefore, no additional network traffic usage was affecting application performance

Testing parameters

As previously mentioned, there are three parameters that were used for testing purposes: Time needed when restoring, Space saved when restoring and Resources used when restoring i.e. memory impact

The results

Time needed when restoring

Numbers and diagrams show us what the current position of ApexSQL Restore is when compared to the leading competitor, using the same testing environment:

Restoring on SQL 2012

Restoring on SQL 2008R2

It is noticeable that the performance difference increases with the size of the test databases. The biggest performance difference is on a large database. This is a significant detail because, in an enterprise environment, database sizes are often more than large

Space saved when restoring

When it comes to saving space, as illustrated below, ApexSQL Restore again takes the lead:

Saved space when restoring on SQL 2012

Saved space when restoring on SQL 2008R2

In all test cases, the results are highly efficient; the numbers are showing that the efficiency ratio does not depend on the database structure. The performance difference is also noticeable

Resources used when restoring

ApexSQL Restore uses less resources in all test cases. Note that the measured parameter is derived from the following formula:

Memory impact * duration (MB*s)

Memory impact - SQL 2012

Memory impact - SQL 2008R2

According to the results, ApexSQL Restore saves time and uses less space and resources then both SSMS and Leading competitor. In some cases, the difference is more than double, demonstrating the application’s overall performance and efficiency

March 18, 2013