After importing database structure to a schema, the database usually changes with time as the development process progresses. As a result, the schema may be no longer in sync with the database structure. Such discrepancies cause problems at run time and they are hard to keep track of manually. Special Schema Designer menu items and other features can help you keep the schema in sync with the database.
The schema comparison/differences tool scans the schema and database structure and shows differences between them in the Output window. To use this tool, complete the following steps:
Contents of the Output window can be copied to the clipboard using the window's context menu. The tool shows only differences for objects and properties that can be imported from the database structure. In effect, the tool compares two schemas: one is the existing schema, and the other is the schema that would result from the import of the database structure if such import would be performed from scratch at the time of comparison. Only tables, fields and relations belonging to the selected connection are processed; therefore, unbound (calculated) fields are ignored, as are unbound tables, or tables and relations bound to other connections.
The additional import tool, Add absent database objects in the Schema menu, allows you to import additional fields or whole tables and additional relations that could be added to the database after the schema was created from the database structure. This tool does not change any properties of the objects that are already in the schema, so you can safely use it to add new tables, fields and relations as they are added to the database. To use the Add absent database objects tool, complete the following:
The Retrieve all fields action deletes all existing fields and retrieves fields from database structure. There is a confirmation dialog that warns you that this action will delete all existing fields with all their settings. The second action, Add absent fields, does not change the existing fields or their properties in any way. It adds the fields that exist in the database table but do not exist in the schema table. Usually those are fields that were added to the table after the schema was created.