Data Source Capability Matrix
Which of the 31 data sources support which capabilities, read from the connector source.
Not every data source can do everything. A connector declares the capabilities it implements, and Infohub only offers you the features its declared capabilities support — which is why an option that exists for one data source is simply absent for another.
This table is read from the connector source at v7.2.0, so it says what the shipped code declares rather than what the sales sheet claims.
What the capabilities mean#
| Capability | What it gives you |
|---|---|
| Refresh triggers | The source can be asked which periods changed, so retrieval is driven by the source rather than the clock. This is what a Refresh Trigger needs. |
| Raw values | Returns individual timestamped values over a period. Required for raw-value retrieval and for tag-level calculations that work on the raw stream rather than an interval summary. |
| Configuration migration | Existing connection configuration is upgraded automatically when the connector version changes. |
| Namespace browsing | The source exposes its tag tree, so you pick tags in Flow Config rather than typing paths. |
| Attribute values in bulk | Reads attribute values for many timestamps in one call. |
| Server-side period value | Infohub asks the source for a single value for the interval and lets the source do the summarising, instead of pulling raw values and aggregating them itself. |
| Friendly details | Renders a human-readable description of a selected item in Flow Config. |
| Test button | The connection dialog can test the connection before you save it. |
| Bulk period values | Adds a pre-query pass so a run of intervals is fetched in one exchange with a resolution and timeout, rather than one round trip per interval. |
| Model attributes in queries | Model attribute values are passed to the connector, so a query can be parameterised per asset. |
| Lazy namespace browsing | Loads the tree branch by branch as you expand it, and supports find-next searching — how a namespace with hundreds of thousands of tags stays usable. |
| Catalogues | Lists the databases or catalogues on the server so you can choose one when configuring the connection. |
| Attribute value | Reads a text attribute at a timestamp — batch ids, product codes, operator names — for attribute measures and event attributes. |
| Persistent connection | Holds the connection open between retrievals instead of reconnecting each time. |
| Late data detection | Reports which periods changed since a given time, so Infohub can recalculate values whose source data was edited or arrived late. |
| Enumerations in bulk | Resolves many ordinals at once. |
| Filter data | Returns a second stream used to filter or condition the first, so values are only kept while the filter holds. |
| Realtime source | The connector receives values as they are published rather than being polled for a period. Realtime sources feed the value stream continuously instead of answering a time-range query. |
| Tag metadata | Reads and updates tag metadata — engineering units, descriptions — alongside the values. |
| Namespace write-back | Creates, renames and deletes folders and items in the source itself, not just in Infohub. |
| Item reference | Produces the canonical reference string for an item. |
| Enumerations | Resolves a numeric ordinal to its text, so a state code stored as a number reads as a state name. |
| Tag configuration | The connector carries its own per-tag configuration rather than relying solely on the namespace. |
| Instance details | The connector is told which Infohub instance it is running under. |
Which data sources support what#
Refresh triggers — 22 of 31
AWS Timestream · Canary Historian · Canary Historian V24 · Flow Historian Simulator · Ignition Historian · InfluxDB · Microsoft SQL Database · MySQL Database · Netilion · OPCHDA Historian · OPCUA Historian · Oracle Database · PostgreSQL Database · Siemens Process Historian · Snowflake · Web Service · Wonderware Historian · Wonderware Historian 2017 · Wonderware InTouch · Wonderware MES · Wonderware Online · eWon
Raw values — 21 of 31
AWS Timestream · Canary Historian · Canary Historian V24 · Flow Historian Simulator · Ignition Historian · InfluxDB · Microsoft Excel · Microsoft SQL Database · MySQL Database · OPCHDA Historian · Oracle Database · PostgreSQL Database · Siemens Mindsphere · Siemens Process Historian · Snowflake · Timebase Historian · Web Service · Wonderware Historian 2017 · Wonderware InTouch · Wonderware Online · eWon
Configuration migration — 18 of 31
Canary Historian · Canary Historian V24 · Flow Historian Simulator · Ignition Historian · InfluxDB · MQTT · Microsoft SQL Database · MySQL Database · OPCHDA Historian · OPCUA Historian · Oracle Database · PostgreSQL Database · Siemens Process Historian · Snowflake · Web Service · Wonderware Historian · Wonderware Historian 2017 · Wonderware Online
Namespace browsing — 17 of 31
AWS Timestream · Flow Historian Simulator · Ignition Historian · Metering Online · Microsoft SQL Database · MySQL Database · Netilion · Oracle Database · PostgreSQL Database · Siemens Mindsphere · Siemens Process Historian · Snowflake · Timebase Historian · Wonderware InTouch · Wonderware MES · Wonderware Online · eWon
Attribute values in bulk — 15 of 31
AWS Timestream · Canary Historian · Canary Historian V24 · Flow Historian Simulator · Ignition Historian · InfluxDB · Microsoft SQL Database · MySQL Database · OPCHDA Historian · OPCUA Historian · Oracle Database · PostgreSQL Database · Snowflake · Wonderware Historian · Wonderware Historian 2017
Server-side period value — 15 of 31
AWS Timestream · Ignition Historian · InfluxDB · Microsoft Excel · Microsoft SQL Database · MySQL Database · Netilion · OPCHDA Historian · Oracle Database · PostgreSQL Database · Siemens Mindsphere · Snowflake · Web Service · Wonderware MES · eWon
Friendly details — 14 of 31
AWS Timestream · Canary Historian · Canary Historian V24 · Flow Historian Simulator · Ignition Historian · InfluxDB · Metering Online · Microsoft SQL Database · MySQL Database · OPCHDA Historian · Oracle Database · PostgreSQL Database · Snowflake · Wonderware Historian 2017
Test button — 13 of 31
AWS Timestream · Apache Kafka · Canary Historian · Canary Historian V24 · Ignition Historian · InfluxDB · Microsoft SQL Database · MySQL Database · OPCHDA Historian · Oracle Database · PostgreSQL Database · Siemens Mindsphere · Snowflake
Bulk period values — 11 of 31
Canary Historian · Canary Historian V24 · Flow Historian Simulator · Metering Online · OPCHDA Historian · Siemens Process Historian · Wonderware Historian 2017 · Wonderware InTouch · Wonderware MES · Wonderware Online · eWon
Model attributes in queries — 9 of 31
AWS Timestream · Ignition Historian · Microsoft Excel · Microsoft SQL Database · MySQL Database · Oracle Database · PostgreSQL Database · Snowflake · Web Service
Lazy namespace browsing — 8 of 31
Canary Historian · Canary Historian V24 · InfluxDB · OPCHDA Historian · OPCUA · OPCUA Historian · Wonderware Historian · Wonderware Historian 2017
Catalogues — 7 of 31
AWS Timestream · Microsoft Excel · Microsoft SQL Database · MySQL Database · Oracle Database · PostgreSQL Database · Snowflake
Attribute value — 7 of 31
Netilion · Siemens Process Historian · Web Service · Wonderware InTouch · Wonderware MES · Wonderware Online · eWon
Persistent connection — 6 of 31
Canary Historian · Canary Historian V24 · Siemens Mindsphere · Wonderware Historian · Wonderware Historian 2017 · eWon
Late data detection — 5 of 31
Microsoft SQL Database · MySQL Database · Oracle Database · PostgreSQL Database · Snowflake
Enumerations in bulk — 5 of 31
Microsoft SQL Database · MySQL Database · Oracle Database · PostgreSQL Database · Snowflake
Filter data — 5 of 31
Canary Historian · Canary Historian V24 · Flow Historian Simulator · OPCHDA Historian · Wonderware Historian 2017
Realtime source — 5 of 31
Apache Kafka · MQTT · OPCUA · Telegraf · Thin Manager
Tag metadata — 4 of 31
Apache Kafka · MQTT · Telegraf · Thin Manager
Namespace write-back — 1 of 31
Wonderware Historian
Item reference — 1 of 31
OPCHDA Historian
Enumerations — 1 of 31
AWS Timestream
Tag configuration — 1 of 31
OPCUA
Instance details — 1 of 31
Wonderware Historian
Reading this table#
- A capability a connector does not declare is not a defect. Most sources genuinely cannot answer the question — a flat file has no namespace to browse, and a broker has no history to replay.
- Declaring a capability means the connector implements the interface. It does not promise the server on the other end is configured to allow it; permissions and licensing still apply.
- If a feature you expect is missing in Flow Config, check this table before raising it: the field is usually hidden because the connector never declared the capability behind it.