# Tag ID Mismatches in sqlth\_te

**URL:** <https://forum.inductiveautomation.com/t/tag-id-mismatches-in-sqlth-te/87970>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [March 27, 2024, 2:16pm UTC](https://forum.inductiveautomation.com/t/tag-id-mismatches-in-sqlth-te/87970 "2024-03-27T14:16:39Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Connor\_Sims](https://avatars.discourse-cdn.com/v4/letter/c/c77e96/32.png) [@Connor\_Sims](https://forum.inductiveautomation.com/u/Connor_Sims)\
**Post date:** [March 27, 2024, 2:16pm UTC](https://forum.inductiveautomation.com/t/tag-id-mismatches-in-sqlth-te/87970/1 "2024-03-27T14:16:40Z")

</div>

With a tag history splitter configuration using two database sources - is there a known behavior that, for select tagpaths, Ignition may retire+create a new tag ID in one data source, but not the other?

I'm finding Ignition will retire tag ID's for certain tagpaths in our secondary data store, SCADA\_History.sqlth\_te, but will leave the original tagpath in the primary data store, SCADA.sqlth\_te. This increments the tag id only in the secondary data store, so all newly created tags will have offset IDs between the two.