In place of SQL Server databases, Harmony Enterprise provides an option to create or export to an .hldb file. These .hldb files can be imported into Harmony Enterprise SQL databases, or other .hldb files in order to merge or replace your work.
Whether or not information is overwritten, appended, or merged into the existing database, is dictated by the Options dialog box. Wells and groups that were originally extracted from Harmony Enterprise have an ID that requires them to be merged back to the original. Analyses that have been modified from the original are overwritten, and new analyses are appended.
Note: With an SE license, you cannot import entities from an .hldb file.
The following items are not imported:
- GIS layers (shape, image, bubble, annotations, flags)
- Comparison plots
- Classified analyses not associated with the active reference date
- Report sets
- Monitor results
Since options, templates, and workflows are user-specific and saved on your workstation, these items are not imported.
To import from an .hldb file:
1. Click the Import icon (
) and select .hldb file.
2. Browse to your .hldb file and click Open.
Your imported entities are brought into your existing database from the entities in the .hldb file.
3. Review your merge options in the Confirm Import Merge Options dialog box. To change your settings, click the Options icon (
), which opens the Options dialog box. To proceed without make changes, click OK.
Note: We do not use the Updating Data | Analysis Data settings in the Options dialog box. Instead, when you import from .hldb files (local database files), if an analysis or worksheet already exists, it replaces the existing copy.
Custom groups
If you import an .hldb file with a custom group that has the same name and ID as one found in the database, the custom group is merged in the database.
If you import an .hldb file with a custom group that has the same name but a different ID from one in the database, a new custom group is created with a filename appended by a numeric (for example, <custom_group>(1), <custom_group>(2), etc).