Running Global Projects
Using Extracts with Global Projects : Using Extracts in MODEL : Refreshing an Extract
If changes have been made to the data in an extract, the changes will not be visible in lower extracts unless these extracts are refreshed. The REFRESH command operates on a database, and it refreshes the database to look at the latest state of the parent extract.
If the changes are in the master and need to be made available in an extract several levels down, the FULLREFRESH command should be issued at the extract. This refreshes each extract in turn, starting with the extract directly beneath the master database, continuing down to the lower extracts, and ending with a refresh of the extract itself.
|
•
|
GETWORK will get changes made to databases in the current MDB.
|
|
•
|
REFRESH will get changes made to the parent extract only of an extract in the MDB.
|
|
•
|
FULLREFRESH will get changes made to all the extract ancestors of an extract in the MDB.
|
The REFRESH command will only refresh from databases local to the satellite. Therefore, if a secondary database has not yet been automatically updated with changes made to the database at the primary location, then these changes will not yet be visible at the local satellite. Extracts below the database will only see the latest version of the secondary database when they are refreshed. To see the changes made to the primary database, wait for the next scheduled automatic update before refreshing.
