Selecting objects to synchronize

After you have reviewed the comparison results, you can select the objects you want to synchronize and run the synchronization wizard.

Note

When you select the Source and Target, the sync operation only applies changes to the target database, while the source database keeps unchanged.

Selecting rows to synchronize

By default, all rows are selected for synchronization.

Postgres sync databases - Selecting rows to synchronize

Use the checkboxes to undo the selection of rows for synchronization.

You can also use the Operation drop-down menu to select objects:

PostgreSQL compare two database schemas - Operation drop-down menu

  • None is set by default for identical objects and cancels the selection of an object for synchronization. You can change it to Drop.

  • Drop is set by default for objects with the Only in Target status and means that the object will be dropped in the target schema. You can change it to None.

  • Create is set by default for objects with the Only in Source status and means that the object will be created in the target schema. You can change it to None.

  • Update is set for objects with the Different status and changes the target object according to the source object. You can change it to Drop or None.

Object status

dbForge Schema Compare for PostgreSQL automatically sets different statuses for compared objects to help you quickly analyze the differences. The statuses are as follows:

  • Only in Source - schema object exists in the source schema and does not exist in the target schema.
  • Only in Target - schema object exists in the target schema and does not exist in the source schema.
  • Different - schema objects with the same names exist in both schemas but have different DDL.
  • Equal - identical objects exist in both schemas.
  • Inconsistent - objects are different, but the target object can not be created or updated due to incompatibility between the source and target servers. For example, if a source table contains a BIT column and a target server does not support BIT columns, the table status will be inconsistent.
  • Unknown - object metadata cannot be retrieved, so its status is unknown.

Synchronizing databases

Note

Schema synchronization can not be rolled back. It may alter or drop schema objects in your target schema. It is highly recommended to back up the target database before synchronization.

After you have selected objects, you can run the process of synchronization.

To synchronize the objects

1. To open the Schema Synchronization Wizard, click Synchronization arrow Synchronize objects to the target database.

PostgreSQL synchronize databases - Click synchronize button

2. Select one of the output options to manage the synchronization script:

  • Open the synchronization script in the internal editor
  • Save the script to a file
  • Execute the script directly against the target database

Synchronize PostgreSQL databases - Synchronization wizard

3. To close the wizard and complete the synchronization process, click Synchronize.

Want to Find out More?

Overview

Overview

Take a quick tour to learn all about the key benefits delivered by dbForge Schema Compare for PostgreSQL.
Ready to start using dbForge Schema Compare for PostgreSQL?