Queries, reports, report formats, and preferences are no longer database specific. You see the same sets of these items no matter which development database you log on to. Existing items in your development databases are automatically transferred to your central CR database. You do not need to explicitly migrate them.
If there are name conflicts between items in different databases, the conflicting items are automatically renamed. For example, if one development database used to contain Report A and Report B, and another contained Report B and Report C, after upgrading to a central server, your central CR database contains Report A, Report B, Report B (2), and Report C.
If you are converting an existing database into to your central CR database, the CRs are not affected. However, the CRs in your development databases are not initially visible in a central server.
To make CRs visible, migrate them to the central CR database.
When you migrate CRs from a development database, the system completes the following actions:
All CRs that are local to the development database are transferred to the central CR database and made local. Their modifiable_in attributes are changed. In some cases, non-modifiable copies of the CRs remain in the development database. Assume that CRs are deleted from that development database. Non-local CRs are skipped. You must migrate their development databases separately to transfer them.
If you have any objects associated to CRs that are not intended to be transferred to the central CR database, do not migrate.
These relationships remain intact in your central CR database. If you have CRs related to non-local CRs because you previously used Distributed Configuration Management (DCM), the non-local CRs are not migrated yet. They do not show up as related CRs. When the databases that they are local to are migrated, then the CRs and relationships show up.
Associated tasks and their associated objects remain in the development database, but the relationships from CRs to tasks are preserved. When a CR with associated tasks has been migrated, you can see its original associated tasks.