Updating

Updating is an ongoing process for propagating changes from records in the DMSII database to the secondary database. DATABridge uses the audit files created by DMSII to extract and apply the updates to the secondary database.

Updating can be accomplished using exclusively DATABridge Host software. Alternatively, you can incorporate DATABridge Client software to perform this function.

Host-based updating

In this method of updating, you run the Span Accessory to retrieve updates from DBEngine and then write those records to one or more data files on the host. You then transfer those files to the new location and load the data into a secondary database.

An advantage of using host-based updating is that you can replicate DMSII data to any system, even if Attachmate has not developed a DATABridge Client for that particular system.

A disadvantage of this method is that it puts more responsibility on you to deliver and process the updates in the data files.

Client-based updating

In this method of updating, a DATABridge Client program (typically running on another system) communicates with the Server Accessory, which retrieves information from DBEngine.

The DATABridge Client requests updates from the Server Accessory, which in turn calls the appropriate entry points in DBEngine to retrieve the modified records. The DATABridge Client program then updates the client database with those changes.

Loose vs. Tight Replication

You can determine how current to make your secondary database by choosing between a loose replication or a tight replication. Regardless of which you choose, only DATABridge updates should be allowed on the secondary database. This maintains data integrity between the primary database and the secondary database.