Troubleshooting
Why DB Table Historian is missing on Ignition 8.0
Short answer
The DB Table Historian provider type does not exist in any Ignition 8.0.x gateway, regardless of module or license state: the type ships with the 8.1 line. The same configuration that lacks it on v8.0.2 shows it and populates MySQL on v8.1.4, so the fix is upgrading the gateway to 8.1.x and creating the provider on the existing connection.
On this page
- Why is DB Table Historian missing on Ignition 8.0?
- Is the Tag Historian module or its license the cause?
- Is the MySQL database connection at fault?
- Should you upgrade the gateway or stay on 8.0?
- How do you upgrade a v8.0.2 gateway to 8.1.x?
- How do you create the DB Table Historian provider on 8.1?
- How do you confirm the historian is writing to MySQL?
- Questions asked
The DB Table Historian entry is missing because the gateway runs the 8.0 line: the provider type does not exist anywhere in 8.0.x, whatever the module or license shows. It ships with Ignition 8.1, so the fix is upgrading the gateway to a current 8.1.x build and then creating the provider on the existing MySQL connection — no setting, reinstall or schema change on the 8.0 gateway can produce it. This page walks the checks that rule out the module, the license and the datasource, gives the version test that decides the case, and then covers the upgrade, the provider creation and the query that proves rows are actually stored, using the observed pair v8.0.2 (entry absent) and v8.1.4 (entry present, history populating MySQL) as the reference.
Why is DB Table Historian missing on Ignition 8.0? #
The type does not exist in the 8.0 line: DB Table Historian ships with Ignition 8.1, so no license, module reinstall or database change can make the entry appear on a v8.0.x gateway.
The provider list on the Historical Tag Providers page is an inventory of what the gateway build contains, not of what a license unlocks, which is why a valid, activated module still cannot show the entry. The reported case carries the full signature: Tag Historian v3.0.2 valid and activated on v8.0.2, the entry absent, while the identical configuration on a v8.1.4 gateway lists DB Table Historian and populates MySQL. There is nothing on the 8.0 gateway to repair — no hidden flag, no module reinstall, no database setting — because the code for the type is not in the build.
| Check on the server | Reading | What it tells you |
|---|---|---|
| Gateway version on the status page | 8.0.2 | Below 8.1, so the type cannot appear |
| Config > System > Modules | Tag Historian v3.0.2, valid and activated | Module and license are not the cause |
| Historical Tag Providers list | DB Table Historian absent | Expected on the 8.0 line; nothing to repair |
| Same configuration on v8.1.4 | DB Table Historian present, MySQL populating | The gateway version decides the list |
| Alarm Journal on MySQL | Alarms stored in the database | Datasource credentials, driver and path are proven |
Is the Tag Historian module or its license the cause? #
On the affected server, Tag Historian v3.0.2 showed valid and activated on v8.0.2 with the entry still absent, which is the signature of a version limit rather than a module or licensing fault.
Check two things before accepting that. Read the running version on the gateway status page first, because an 8.0.x reading ends this branch before it starts. Then open Config > System > Modules and confirm Tag Historian is loaded, not faulted, and shows an activated license: a module installed but faulted removes provider types on any version, so the check is worth the two minutes even where the module reads valid. If the module is running and the gateway still reads 8.0.x, the missing entry is a version limit and nothing else — vendor support reached the same conclusion on this case.
Is the MySQL database connection at fault? #
A working Alarm Journal already proves the datasource, because credentials, driver and network path are validated by alarms reaching MySQL, and the provider reuses that connection unchanged with no preparation needed before the upgrade.
Separate three states so the database is not blamed for the version's absence: the connection logging in, which the Alarm Journal already proves; the provider's configuration, which is created after the upgrade; and rows actually stored, which only a query confirms. Under Config > Databases > Connections the status should read Valid, and no schema or account change is needed for the upgrade itself, so leave MySQL and the connection definitions exactly as they are.
Should you upgrade the gateway or stay on 8.0? #
Upgrade, because staying on 8.0.2 pins you to the provider types the 8.0 line shipped with no path to DB table storage, while the move to 8.1.x keeps the same MySQL connection and carries the configuration forward.
Worked example — the version test, changing one input at a time:
- Gateway A: v8.0.2 with Tag Historian v3.0.2 activated — the Historical Tag Providers list has no DB Table Historian entry.
- Gateway B: v8.1.4 with the same module and the same MySQL setup — the list shows DB Table Historian, and tag history populates MySQL.
- The comparison: 8.0.2 < 8.1.0, so Gateway A predates the release line that carries the type. One input — the gateway line — changed, and the outcome changed with it, which makes the gateway version the deciding input and the upgrade the fix.
Choose the newest 8.1.x build available from the vendor rather than the minimum: the 8.1 release notes carry DB-historian maintenance through the line — a cache-rebuild fix for DB historians is documented at v8.1.14 — and the offline reference build in this case was v8.1.4.
How do you upgrade a v8.0.2 gateway to 8.1.x? #
Take a full gateway backup, confirm license coverage with the vendor, then run the 8.1.x installer over the existing install and let it bring the matching Tag Historian build; module files are not carried across major versions.
Treat the window as a planned historian outage: history collection stops while the gateway restarts, so pick a quiet production period. Then:
- Take a full gateway backup (.gwbk) and note the installed modules and license key with the change record.
- Confirm with the vendor that the license covers the 8.1 line, so a reissue or reactivation is settled before the window, not during it.
- Download the 8.1.x installer from the vendor's download site and run it over the existing install, installing the Tag Historian build that matches 8.1 with it.
- After the restart, confirm the status page reads 8.1.x and Config > System > Modules shows Tag Historian running and licensed.
- Check the MySQL connection still reads Valid under Config > Databases > Connections.
How do you create the DB Table Historian provider on 8.1? #
Open Config > Tags > History > Historical Tag Providers, create a new provider, choose DB Table Historian from the type list, select the existing MySQL connection as the datasource, and configure the table and column mappings the type asks for.
The 8.1 documentation describes DB Table Historian as a bridge between tables in a database connection and the Tag Historian module, configured by mapping the columns of those tables, so the fields the provider asks for at creation are the mappings, not a new schema. Save the provider, then point the history provider setting on the tags that should use it at the new provider name. The upgrade does not move or rename your live tags, and how they are organized — a single tag provider versus several, one per PLC — is a separate architecture choice this change does not touch.
How do you confirm the historian is writing to MySQL? #
Creation alone proves nothing: enable history on one test tag, force several value changes, then query the connection for rows carrying timestamps newer than the test start, and view the tag in a trend chart.
- Enable history on one test tag, with a short sample rate or on-change mode.
- Force several value changes and note the times.
- Query the MySQL schema for the historian's rows and look for inserts stamped after the test start.
- Open a trend chart on the test tag and confirm the trace draws the new samples.
A present entry with tables that never appear on the connection is a downstream fault, not a version one: why Ignition tag historian tables are not created picks that thread up. If provider creation fails against MySQL itself, fixing historian table creation failing on MySQL over ODBC covers the datasource side. Once rows are confirmed, set a retention boundary so the tables do not grow unbounded — setting historian pruning and retention for Ignition tag history is the follow-up.
Questions asked
Can Ignition 8.0 store tag history in MySQL at all?
Yes. The standard Tag Historian provider on 8.0 writes its own schema tables to a configured MySQL connection, so storing new tag history in MySQL is not blocked by the version. What 8.0 cannot do is bridge data that already sits in ordinary database tables into tag history; that column-mapping bridge is the DB Table Historian type, which ships with the 8.1 line.
What does the DB Table Historian provider do once it is available?
It bridges tables in a database connection to the Tag Historian module: you map the columns of a table to tag history fields, and history flows through that mapping instead of requiring an application-side rewrite. It is aimed at data that already sits in ordinary tables, such as wide-table logger output, and it is configured through those column mappings on the provider.
Can I reuse the Tag Historian module file from the 8.0 install after upgrading?
No. Module builds are matched to the gateway major version, so an 8.0 module file does not load on an 8.1 gateway, and the reverse. The 8.1.x installer brings the Tag Historian build that matches the new gateway; do not carry the old file across by copy.
Does the Alarm Journal on the MySQL connection prove anything for the historian?
It proves the datasource only. Alarms reaching MySQL show that credentials, driver and network path work, which is exactly what the provider depends on. It says nothing about whether historian rows are stored: schema provisioning happens when the provider is set up, and a confirmed write needs a known tag, a known value change and a matching timestamp in the table.
Can the gateway be rolled back to 8.0 after the upgrade?
The rollback is the pre-upgrade gateway backup: restoring the .gwbk taken before the window returns the v8.0.2 system with its configuration, and the DB Table Historian entry disappears again along with the version. Keep that backup until the 8.1 system has run through a verification window.