Cross Database Working

The base product has the ability to split the design model across several databases, some of which may be read only.

Exporting the model tries to update certain variables associated with the version management. However, if the database is read only, a macro file is produced that should be executed immediately as soon as you have write access to the database.

Important:

This must be performed before any further import procedures are performed.

The file name is built upon the string "updateVersionNos" but with time stamp information attached so that they can be executed in chronological sequence. An example file name might be "updateVersionNos201312593744.mac", which was created at 09:37:44 on 25th January 2013.

Importing an existing, though modified, model is more difficult. Obviously you must have write access to the database. The reference site is created in the same database as the target area specified on the Import window. This allows new items to be transferred between the reference site and the target site using the INCLUDE command.

You should make sure that the incoming data is not to be spread across databases.

If the target area is empty the Compare/Merge processes are bypassed which can be a lot faster when importing large amounts of data.

Users of multi-write databases need to be aware that elements that are to be exported must be claimed out prior to export. All elements that are likely to be affected by importing must also be claimed out.