(Show Contents)

How to Copy Non-Data Dictionary Data between Projects

This procedure applies only to tables that are not included in the data dictionary; that is to say, your project tables and the "afm_" tables that are not afm_fields or afm_tables.

In this procedure, it is assumed that the schema definition for the tables to be copied is the same between the two projects.

Note: It is possible to copy data from one project to another where the schemas differ. However, the success of that transfer will depend on what the differences are and if the destination tables are capable of accepting the data. An example of a potential problem is if the primary key is shorter in the destination database than it is in the source database. In this case, data would be truncated to fit, potentially creating duplicate primary keys, which would not be inserted. An example in which you would not have a problem is if the destination database has more columns that the source database. Assuming the destination database allowed null values in those additional columns, the transfer would succeed. In summary, your data transfers will be much more reliable if the schemas are the same for the data you are transferring. If you need to take steps to make the tables consistent, see the topic How to Migrate Schema Changes from one Project to Another.

1. If you don't already have one, create a project for each database. The Database Update Wizard will transfer the data out of one project to CSV files and then transfer the CSV files into the new project.
2. Sign into the project from which you want to copy the data (Project A).
3. Run the Database Update Wizard as follows:

• Transfer Type = Transfer Out
• Specify Tables

  For specific data tables: Use the Named Tables to identify the tables that you want to copy with "Include Validating Tables" checked.

  For project data: Select one or more of the Project Specific-table groupings.

  For application data: Select one of the Application Extension table groupings (except for Data Dictionary).

• Select Start Export.

3. The Database Update Wizard will create a series of CSV files for the specified tables.
4. Sign out of Project A.
5. Sign into the project where you want to copy the data (Project B).
6. Run the Database Update Wizard as follows:

• Transfer Type = Transfer In
• Specify Tables = Use a table specification that imports the desired data tables. You can use the same file specification you used for the export, or you may want to import the data in stages.
• Select Start Import.

Examples

• Suppose you have room and equipment information for your "Houston" building coming in from a remote office. You can use the wizard to copy the data to add the new information from that database to your central database. The wizard will also add any new room or equipment standards that the Houston database requires because Include Validating Tables was selected.
• Suppose the Houston room and equipment information has undergone extensive changes, and some records have been deleted. You will want to update the central database. Do so in two steps:
• In the central database, delete all rooms and equipment assigned to the Houston building. This deletion step is necessary because the import process does not delete records. Performing a simple Transfer In only inserts and updates records.
• Use the Update Database Wizard to copy the data from the Houston database to your central database using the procedure described above. The room and equipment information for the Houston building will now match the information in the Houston database. Any tables other than Rooms or Equipment will be merged—that is, new items will be added to the tables and existing records will be updated to match the data in the .csv file from which you are importing the data.

See Also

How to Transfer Data In (Import)

How to Transfer Data Out (Export)