An example would be a Corporate Catalogue DB used for 12.0 and multiple projects.Ī framework is provided to run all the part upgrades. This means that it is possible for users to continue to work with Foreign DBs, which may be shared with 12.0 or earlier projects and which have not been upgraded, included in their projects. In general these Part Upgrades have been designed to be 'optional' from a user perspective, in that the 12.1 software can work with a database that has not been upgraded and the software will degrade gracefully - that is, the software will continue to work, although new functionality may not be fully present. Each individual change is referred to here as a Part Upgrade. 1.1 Part UpgradesĪ number of changes made in 12.1 require an upgrade to parts of the data model and the database. Note: It is not a requirement that Catalogue Projects need to be upgraded. To perform the upgrade the user must do the following: To prepare a 12.0 project for 12.1 use, a database upgrade is required.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |