Using Database Manager, you can import any database into memory. Importing a database merges it with the database currently in memory.
NOTE: Before you import a database, stop any I/O drivers, OPC servers, or OPC UA server you may have running.
IMPORTANT: The iFIX Database Manager uses ANSI encoding. Configuration Hub supports only UTF-8 encoded files. Prior to importing files that were exported from Configuration Hub into the Database Manager, ensure that the CSV file is in ANSI encoding. To do so, open the CSV file in the Windows Notepad editor and perform a SAVE AS with ANSI encoding selected, and then save the file as a CSV. Likewise, if you want to import a file from the iFIX Database Manager into Configuration Hub, save the file with UTF-8 encoding before importing the file into Configuration Hub.
Typically, you import a database when you want to:
- Change the scanning order of the blocks in the database.
- Combine two databases.
To change the scanning
order of a database's blocks:
- Export a database. For more information about exporting a database, refer to the section Exporting Databases.
- Change the order in which the blocks are listed in the export file. For more information on a database's scanning order, refer to the section Changing a Database's Scanning Order.
- In Classic view, on Database Manager's toolbar, click the New button.
-Or-
In Ribbon view, click the Database Manager button, and then click New.
- Import the edited export file.
This process ensures that only the original database resides in memory when Database Manager imports your database.
To combine two
process databases:
- Export each database.
- Examine each export file. Verify that each block in each database has a unique name. If two blocks have the same name, change one. Remember to also change the text in the Next field of the previous block so that the chain remains intact.
- Into an empty database, import one of the databases you want to merge.
- Import the other database.
Import errors encountered by Database Manager are stored in the file IMPORT.ERR. This file resides in the Database path.
Customizing the Import in the databasemanger.ini
Using the databasemanger.ini file you can customize the import by setting the block allocation size used on import. This value controls the number of incremental block memory allocated during import. The BlockAllocationSize defaults to 1000. The range is between 10-5000. Be aware that a small value causes many more reallocations of memory and can be a performance limiter during large imports.
[Options]
SaveDisplaySettingsOnExit=1
SaveDatabaseOnExit=0
MruListPresent=1
MruListSize=4
PrintInBackGround=0
EnableSprAutoRefresh=0
SpreadsheetRefreshPeriod=
DispSprRowNumbers=1
AutoBlockOnScanPostEdit=0
ModifyBlocksOnMouseDoubleClick=1
Ribbon=1
StatusBar=1
ToolBar=1
BlockAllocationSize=1000
