Import or export tag information

The Historian Database Export/Import Utility (aahDBDump.exe) is a standalone utility to export or import AVEVA Historian configuration information with a text file. Exporting and importing data are two independent operations.

The Historian Database Export/Import Utility is useful when you want to make bulk modifications to the configuration, instead of using the Configuration Editor to edit a single database entity at a time. You would simply export the text file, make the modifications, and then import the changes back to the Historian. The utility is also useful for transferring configuration information from one Historian to another.

You can also use the Export/Import Utility to export the Tag History table. This allows you to view different versions – and corresponding configurations – of the same tag.

You can export/import the configuration information for one or more of the following entities. For some of the entities, the utility supports additional filtering.

The Historian Database Export/Import Utility does not export:

• InTouch node information. If you import tag definitions using the Tag Importer, and then export the database configuration, the node information is not included. If, after exporting, you rebuild the AVEVA Historian database, or want to import the database configuration into a different AVEVA Historian, you must first reimport the tag definitions for the InTouch application before you import the database configuration.

• Tags that have their current editor set to be AVEVA Application Server.

Starting with AVEVA Historian 2012 R2, the Tag table includes the AIHistory and ChannelStatus columns, which were not available in previous versions. If you import a configuration file that was exported using AVEVA Historian 2012 or earlier, the following values are used for these column settings:

• AIHistory = 1

• ChannelStatus = 1

The Historian Database Export/Import Utility requires a client connection to the SQL Server used by the Historian to perform the export and import tasks. However, the Historian does not need to be running.

The Historian Database Export/Import Utility does not maintain spaces in tag names during an export.