DataHub software offers two options for connecting to an ODBC database for writing and querying data: the Database feature and the External Historian ODBC feature (ODBC Historian).
The Database feature is aimed at relatively low-volume applications that need flexibility in the database table schema, and in the triggers and conditions under which data points are written or queried. DataHub ODBC Scripting can be used to provide custom capabilities to the Database feature, as well as to automate many aspects of the interface, including configuring points in bulk.
The ODBC Historian is aimed at recording high-volume time series data, essentially using an ODBC database table as a time-series historian. This is the easier interface for configuring large sets of points, and adding new ones. Writes to the database are also much more efficient.
Here is a point-by-point comparison to help you decide which of these two technologies best matches your needs.
Pros:
Can write to tables with multiple data columns.
Allows substitution expressions for values written to the database.
Enables DataHub ODBC Scripting for database reading and writing.
Built-in store-and-forward.
Flexible trigger and condition options.
Cons:
Every data point must be individually configured. Large data sets are cumbersome.
Pros:
Can write at much higher volumes (~10x more rows than the Database feature).
A single configuration can apply all selected points. You set up the write action once, and then just use a pattern to select all points in the domain. When new points are added to the domain, they are automatically written to the database without requiring any changes to the configuration. This makes database writes more efficient, since a single transaction can write multiple values at a time.
Point selection can be individually or as a regular expression (regex) .
Can automatically modify point names based on a regular expression before writing to the database.
Can forward data from another external historian.
Can be a source for store-and-forward to other historians and MQTT connections.
Can be the destination of forwarding from another historian or a tunnel.
Enables sampling (min, max, mean, etc.).
Enables S-Sharp scripting of values written to the database.
Cons:
Less flexibility in triggers.
No trigger and condition options.
More complex scripting when writing to tables with multiple data columns.