The majority of catalog changes are propagated in the Global Workshare Configuration (GWC). However, if new catalog data is bulkloaded at the Host, the workflow depicted in the illustration below must be conducted on the Host server and on all Satellite servers in the GWC. This procedure regenerates the data that is not propagated to the Satellite and returns the workshare to a synchronized state.
-
The Reports database is a set of views that point to data in other databases. Although the Reports database does not participate in the workshare, it must be kept up-to-date.
-
We do not recommend overwriting the Satellite catalog with a copy of the Host catalog and then linking it to the model. Doing so increases the risk of breaking the workshare.
What do you want to do?