Working with backups

Working with Backup Files

Data Compare for SQL Server provides an option of comparing data between backup files or between databases and backup files. This feature can be useful if you want, for example, to retrieve data from a backup file and compare it with your database without restoring or copying the backup from a remote network.

Comparing and synchronizing backup files

With Data Compare for SQL Server you can:

  • compare a backup file with another backup file or with a database
  • create a synchronization script from a backup
  • update the database from which the backup was created.

Note:

Backup files cannot be modified directly. If you set a backup file as the Target, the Data Synchronization wizard creates a script to update the database from which the backup was created.

If you set a backup file as the Source, and a database is the Target, the database can be synchronized with the backup.

Compatibility with backup files

Data Compare for SQL Server supports:

  • native SQL Server backups

If you want to set up a comparison using a backup you should keep in mind that Data Compare for SQL Server does not support:

  • tables that do not have a primary key, unique index, or unique constraint
  • views
  • computed columns, but you can compare persisted computed columns
  • string representations of CLR types (only binary representation is supported)
  • custom comparison keys, but you can select an alternative unique index, or unique constraint
  • row filtering using the SQL Filter Editor.

Known issues with dbForge Data Compare and backups

  • Data Compare doesn’t support compressed backups
  • Data Compare can not compare partial, filegroup, or transaction log backups as a data source
  • You can not compare differential backups with dbForge Data Compare
  • Data Compare doesn’t support encrypted backups.