Special cases in schema comparison

The article describes special cases you may encounter when comparing specific objects in a schema comparison.

Objects with different owners or schemas

Objects that have identical DDL definitions but belong to different schemas or owners appear in the Different section.

To compare these objects:

1. Open the New Schema Comparison wizard.

2. Go to the Schema Mapping page.

3. Re-map the owners.

4. Click Compare.

Extended stored procedures

dbForge Studio for SQL Server does not support comparing extended stored procedures.

Encrypted database objects

In some SQL Server databases, objects, such as stored procedures, functions, or views, may be encrypted so their definitions are hidden. dbForge Studio cannot read encrypted definitions. You can enable the Decrypt encrypted objects option to decrypt these objects and compare their code.

To compare encrypted objects:

1. Open the New Schema Comparison wizard.

2. Go to the Options page.

3. Select Decrypt encrypted objects.

4. Click Compare.

When this option is selected, dbForge Studio for SQL Server attempts to decrypt the definitions so their scripts can be compared and synchronized. The decrypted scripts appear in the results like any other script.

Warning

For large databases, enabling decryption may slow down comparison due to additional processing.

Logins, certificates, and asymmetric keys

SQL Server applies security restrictions that limit access to certain security objects, including:

  • Logins
  • Certificates
  • Asymmetric keys

Because of these restrictions, dbForge Studio for SQL Server cannot fully compare all properties of these objects. To avoid unnecessary differences in results, you can tell the Studio to ignore them.

To compare these objects:

1. Open the New Schema Comparison wizard.

2. Go to the Options page.

3. Select Ignore logins, certificates, asymmetric keys for users.

When this option is selected, dbForge Studio ignores logins, certificates, and asymmetric keys for users while still synchronizing user properties. Logins for existing users in the target database are preserved.

4. Click Compare.