# Adding tags to sqlth\_te

**URL:** <https://forum.inductiveautomation.com/t/adding-tags-to-sqlth-te/112272>\
**Category:** Ignition\
**Created:** [November 19, 2025, 2:33pm UTC](https://forum.inductiveautomation.com/t/adding-tags-to-sqlth-te/112272 "2025-11-19T14:33:12Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Daniel\_Whitlock](https://avatars.discourse-cdn.com/v4/letter/d/8edcca/32.png) [@Daniel\_Whitlock](https://forum.inductiveautomation.com/u/Daniel_Whitlock)\
**Post date:** [November 19, 2025, 2:33pm UTC](https://forum.inductiveautomation.com/t/adding-tags-to-sqlth-te/112272/1 "2025-11-19T14:33:12Z")

</div>

I encountered a bug where if I change the parent data type of a udt instance it does not update the sqlth\_te database. I am currently stepping through removing the unused tags. Is there a clean way to add in all of the correct tags without just stepping through them one by one? I’m trying to save some time here. It’s looking like this might be the rest of my week

---

<div class="post-metadata">

**Author:** ![anjoroge](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/anjoroge/32/6698_2.png) [@anjoroge](https://forum.inductiveautomation.com/u/anjoroge)\
**Post date:** [November 19, 2025, 5:27pm UTC](https://forum.inductiveautomation.com/t/adding-tags-to-sqlth-te/112272/2 "2025-11-19T17:27:39Z")

</div>

Hi Daniel you could try exporting the tags in Json format so that you are able to modify the tags with the UDT instances and make sure they contain the correct instances and definitions and then re-importing into the designer that way you don’t have to manual go through all the tags only change the ones you need too.

---

<div class="post-metadata">

**Author:** ![justin.brzozoski](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justin.brzozoski/32/13452_2.png) [@justin.brzozoski](https://forum.inductiveautomation.com/u/justin.brzozoski)\
**Post date:** [November 19, 2025, 6:46pm UTC](https://forum.inductiveautomation.com/t/adding-tags-to-sqlth-te/112272/3 "2025-11-19T18:46:12Z")

</div>

I can’t promise it’s a fully supported action, but in the past when I needed questional sqlth\_te entries to stop being used, I manually set all of their retirement dates to slightly in the future and Ignition noticed and made new ones as needed. Multiple sqlth\_te entries for the same tag are allowed, even on the same time span.

---

<div class="post-metadata">

**Author:** ![Daniel\_Whitlock](https://avatars.discourse-cdn.com/v4/letter/d/8edcca/32.png) [@Daniel\_Whitlock](https://forum.inductiveautomation.com/u/Daniel_Whitlock)\
**Post date:** [November 20, 2025, 2:47pm UTC](https://forum.inductiveautomation.com/t/adding-tags-to-sqlth-te/112272/4 "2025-11-20T14:47:05Z")

</div>

So you were able to set every tag in the sqlth\_te database to retire slightly in the future, and the database recreated the necessary ones?

---

<div class="post-metadata">

**Author:** ![justin.brzozoski](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justin.brzozoski/32/13452_2.png) [@justin.brzozoski](https://forum.inductiveautomation.com/u/justin.brzozoski)\
**Post date:** [November 20, 2025, 4:15pm UTC](https://forum.inductiveautomation.com/t/adding-tags-to-sqlth-te/112272/5 "2025-11-20T16:15:57Z")

</div>

I didn’t hit EVERY tag with a retirement, but definitely more than I needed to. It was a group of like 1000 tags that were a mix of things I wanted to retire and things that were still being used, and Ignition automatically made new sqlth\_te entries for the ones that were still being used. And querying the history on the tags that kept going includes history from both sqlth\_te entries.
