Skip to main content

Ensure that all model Imports are performed with incremental harvesting (where available)

Not only does incremental harvesting save a great deal of processing time when harvesting, it also consumes orders of magnitude less space. Only those portions of the entire harvested model that have changed are re-imported and written as new versions to the repository database. The rest of the contents are simply reused in the new harvested version.

Information note

This consideration is especially on daily harvesting of large databases, file systems and BI servers.

You will have to go to each of these larger models and ensure that incremental harvesting has not been disabled manually using the “-cache.clear” option in the Miscellaneous bridge parameter. If the option is there, remove it and SAVE the Import Setup . See importing models as well as using “-cache.clear” manually.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!