DataSets - This panel shows all DataSets defined in the Canary Enterprise Historian and provides creation and removal options.
New... - The "New" button will display fields to define the DataSet name and primary path. DataSet names must be more than 1 character in length.
Scan... - The "Scan" button allows the user to select a path where the Enterprise Historian will look for .hdb2 files and automatically create the DataSet accordingly. After entering a Path, click "Scan" to search the directory and if "Include Subdirectories" is checked, any subdirectories.
Remove - If a DataSet is selected from the list below the "Remove" button becomes enabled. Clicking the button will display a confirmation dialog with the option to "Delete All Associated Historical Data" if checked. Click the OK button to remove the DataSet.
Note: DataSet must be closed (no writers or readers) before the Historian will remove it.
DataSet Name - Name of the DataSet.
File Count - Number of files in each DataSet.
Tag Count - Number of tags in each DataSet.
Settings - File management settings for the selected DataSet.
Path: - Directory location where the .hdb2 files will be stored. This path can only be set during DataSet creation. Changing it would require deleting the DataSet and then doing a Scan if .hdb2 files already exist or New if a new location.
Validate - When checked a background thread will validate any files for this DataSet not already validated, except the current file.
Email if no data received in ?? minutes - This requires SMTP Server and email addresses to be setup under Messages > Configuration > Email. If no data is received for any tag in this DataSet within the set minutes an email will be sent to the email recipients.
Roll-Over: - Aside from physical disk corruption the only time a file is susceptible to corruption is when it is opened for writing. Should something happen during one of these writes such as a power failure or machine reset without a controlled shutdown, the file could become unusable. This information should be considered when deciding when to Roll-Over to a new file. For instance, creating a file every day at midnight would only risk the data from the time of the Roll-Over to when the system failure occurred, limiting the possible loss to only a few hours.
- Never - All data will be written into one continuous file.
- Daily: - A new file will be created every day at hh: mm (hours: minutes) after midnight.
- Weekly: - A new file will be created at hh: mm after midnight on the selected day of the week.
- Hourly: - A new file will be created starting at 00:00 - 24:00 (24 hour time) every 2, 3, 4, 6, 8 or 12 Hours. This is to accommodate 1 file per shift.
- Custom: - A new file will be created every 0-100, Minutes, Hours or Days.
- Size: - A new file is created when the current file exceeds 10 - 500 megabytes.
Roll-Up: - Roll-Up is a background operation to take files at the Roll-Over rate and combine them into Daily, Weekly, Monthly or Quarterly files. Never leaves the files as the Roll-over has created.
This option can be most valuable to customers with large quantities of tags as the tag information is duplicated in each file. If the existing file and the next file to be rolled up exceed 500 MB, the operation will not start and a 2nd Roll-Up file will begin for the time period. Roll-Up does not Roll-Up the last file in the DataSet.
Delete: - Files with a creation time older than 1 - 365 Days, Months or Years will be deleted at the time when a Roll-Over or a Mirror, Snapshot occurs. Never will keep all files.
Note: Do not make this setting less than the time of a Roll-Up or the Roll-Up file will be deleted with all the data up to the current file.
Background Validation - Checks each DataSet for files to be automatically validated. The global validation can be disabled for all DataSets by unchecking this box.