# History tag table sqlth\_te retired and fingerprint columns

**URL:** <https://forum.inductiveautomation.com/t/history-tag-table-sqlth-te-retired-and-fingerprint-columns/49543>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [August 4, 2021, 11:39am UTC](https://forum.inductiveautomation.com/t/history-tag-table-sqlth-te-retired-and-fingerprint-columns/49543 "2021-08-04T11:39:32Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Wouter](https://avatars.discourse-cdn.com/v4/letter/w/e99b99/32.png) [@Wouter](https://forum.inductiveautomation.com/u/Wouter)\
**Post date:** [April 29, 2022, 10:23am UTC](https://forum.inductiveautomation.com/t/history-tag-table-sqlth-te-retired-and-fingerprint-columns/49543/4 "2022-04-29T10:23:18Z")

</div>

We’ve had the same problem and we noticed that this post: [[What Causes a History Tag to be Retired - #2 by PGriffith](https://forum.inductiveautomation.com/t/what-causes-a-history-tag-to-be-retired/18933/2)] doesn’t seem to be relevant anymore. In our project tags only get retired if the history is true and the tag gets deleted. If you disable the tag or turn history off and then delete the tag the retire column will stay null forever.

Which is a problem for us since the tag browser tree component will show these non-retired tags. Has anyone found a solution for this? Since now our only option seems to be to manually retire each tag in the database by adding a random number to the retire column.

---

_[View the full topic](https://forum.inductiveautomation.com/t/history-tag-table-sqlth-te-retired-and-fingerprint-columns/49543)._
