ApexSQL Log 2013 vs. 2011 performance testing: the results are in

At ApexSQL we constantly strive to improve our tools. We optimize the technology, improve existing features and options, and introduce new ones. When it comes to a SQL Server transaction log reader, performance is critical. This is why the recent performance breakthroughs in ApexSQL Log 2013 are so important and exciting

We recently performance tested ApexSQL Log 2013 vs. 2011
The same tests, in the same test environment were run with both versions of ApexSQL Log

Test setup

Two different databases were used for testing

The first database contained 1,000 tables with 1,000,000 transactions
The second database contained 10,000 tables with 10,000,000 transactions
Each table in every database had 1,000 transactions created in the following sequence – 5 inserts, 5 updates, 2 deletes

All tests were done on a local PC, where the SQL Server instance hosting test databases was installed, so no network traffic affected the tests. No concurrent sessions or applications were running

System specifications:
Windows Server 2012
SQL Server 2012 x64 Developer edition
CPU Intel core I7 – 3537 2.00 GHZ
RAM: 6GB RAM DDR3
HDD: Western digital 1TB

Performance testing and results

Loading time
We measured the time from the moment when the Open results in the grid option had been selected, until the moment all records were shown in the ApexSQL Log main grid

In the first test, we read only data operations

In the second test, we read both data and schema operations

Export to CSV
We measured the time from the moment the Export to CSV option in ApexSQL Log main menu had been selected to export all the records shown in the ApexSQL Log main grid, until the moment a notification that the CSV file was generated is shown

Export to XML
We measured the time from the moment the Export to XML option in ApexSQL Log main menu had been selected to export all the records shown in the ApexSQL Log main grid, until the moment a notification that the XML file was generated is shown

Creating an undo script
We measured the time from the moment the Create UNDO script option in ApexSQL Log main menu had been selected to create an undo script for all the records shown in the ApexSQL Log main grid, until the moment the generated undo file was shown in the script editor

Creating a redo script
We measured the time from the moment the Create REDO script option in ApexSQL Log main menu had been selected to create a redo script for all the records shown in the ApexSQL Log main grid, until the moment the generated redo file was shown in the script editor

Grid filtering
The biggest performance improvement was measured for grid filtering. For this test, after all records had been shown in the ApexSQL Log main grid, we checked/unchecked several options in the Data operations (DML), Schema operations (DDL), and Users filters in the Grid filter. We measured the time from the moment Apply was clicked, to apply the filter settings to the records in the main grid, until the filtered results were shown in the main grid. For all tests, the same options in the filters were checked and unchecked

See our infographic for graphical presentation of the results

As the results show, ApexSQL Log 2013 is faster in all tested scenarios