How DBUpdater Works

Here follows the steps required to update all customer databases together with applications.

Development team extracts database schema. The schema will be saved in xml files and then packaged.

A configuration file can be added to the package which contains update directives concerning "how and what" objects update.

Package is send to customers together with new applications executables.

In the customer machine, a specialized comparison routine is launched (manually or automatically inside the application executable) which unpack the package, reads configuration and executes database comparison with the XML schema database.
The comparison routine generates a file containing all Sql statements required to synchronize the database and run it.

All these steps can be done in "quiet mode".
But if you want to give more control to the user (or reseller), specialized procedures allows to:
- report variations;
- manage sql statements
- show / hide console window
- show / hide progress info window
- show / fix / report warnings
- asks confirmation for all "dangerous" operations.
- allow / inhibit update of objects categories (i.e., don't update stored procedures at all)
- allow / inhibit deletion of unused objects (tables, fields, indexes, .)
- skip objects with a "special name"
- make a backup before sync
- defines folders for packages, backup, .
- provides a hand-wrote file to run sql statements before and / or after update phase