<< Click to Display Table of Contents >> Navigation:  General Functions > Performing Local Backup > How Data is Transferred > Tables that are not fully synchronized

For the most part, the SFT client will keep your local database fully synchronized with data on the MIE.  This allows you to create ad-hoc reports against the data in your local database, knowing that it is a replica of what is on the MIE.  There are some tables, however, that are meant to hold permanent historical records, such as the catch point staging offline and/or archive tables.  For tables such as these, the SFT client will ensure that records that exist on the MIE are copied down to your local database, but it will not delete any records from the local database that no longer exist on the MIE.  This is referred to as partial synchronization.  This allows you to maintain an ongoing permanent historical record locally, knowing that, due to the MIE's retention policy, that eventually the MIE will purge older records.  The following tables are set for partial synchronization:

 

•MIE-AT Asset Status Snapshots

•MIE-AT-IMAC Staging (catch point history live storage table)

•MIE-AT-IMAC Staging Offline (catch point history offline storage table)

•MIE - Request Orders

•MIE - Request Order Items

•MIE - Request Order Answers