For the best web experience, please use IE11+, Chrome, Firefox, or Safari

ApexSQL Diff FAQ

General

The minimum permissions required to compare SQL objects are:

  • Public role membership on both the source and the destination SQL instances,
  • CONNECT and
  • VIEW DEFINITION on both the source and the destination databases

In addition to the above:

  • CONTROL has to be granted on the destination database to execute the synchronization script

Either native or natively compressed full and differential database backups can be compared using ApexSQL Diff Professional

Yes. The minimum permissions required to compare encrypted objects are:

  • Public role membership on both the source and the destination SQL instances,
  • CONNECT on both the source and the destination databases
  • VIEW ANY DEFINITION on both the source and the destination SQL instances

In addition to the above:

  • CONTROL has to be granted on the destination database to synchronize encrypted objects

No. The tool is fully functional for the 14 day period

No. There is virtually no limit to the number of objects the tool can process

SQL Server support

ApexSQL Diff supports SQL Server Express, Standard, and Enterprise editions

Microsoft SQL Server 2017, 2016, 2014, 2012, 2008, and 2005

ApexSQL Diff integrates into SQL Server Management Studio 17, 2016, 2014, or 2012
You can use the latest full-featured backwards compatible SQL Server Management Studio for free. Click here

Yes. ApexSQL Diff fully supports Azure SQL Database V12

The tool can be used directly from SSMS alongside any other ApexSQL add-in

Yes. However, please note:

  • This functionality is available in ApexSQL Diff Professional only
  • The synchronization script will be compatible with the target SQL Server version. For instance, if you are synchronizing a SQL Server 2012 backup to a SQL Server 2005 database the synchronization script will not attempt to create FileTables in the destination database, even if they are present in the backup itself

The DROP/CREATE pair will be used instead of ALTER for the following scenarios:

  • File group differences exist
  • ANSI options are different
  • Identically named columns contain incomparable data types
  • Identity columns differences exist
  • Columns are ordered differently
  • XML column differences exist

Source control systems support

  • Git
  • Mercurial
  • Perforce
  • Subversion
  • Team Foundation Server

Use ApexSQL Build to create a database containing the versioned objects from scratch in just a few clicks