# What Causes a History Tag to be Retired

**URL:** <https://forum.inductiveautomation.com/t/what-causes-a-history-tag-to-be-retired/18933>\
**Category:** Ignition\
**Created:** [July 23, 2018, 3:29pm UTC](https://forum.inductiveautomation.com/t/what-causes-a-history-tag-to-be-retired/18933 "2018-07-23T15:29:55Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [July 23, 2018, 5:03pm UTC](https://forum.inductiveautomation.com/t/what-causes-a-history-tag-to-be-retired/18933/2 "2018-07-23T17:03:36Z")

</div>

Tags should be retired in `sqlth_te` when the associated realtime tag is disabled, deleted, or has history turned off. Unfortunately, there was a bug with this behavior (fixed in a fairly recent version) so it’s possible you’re looking at older records that will not retroactively retired, or even that you’re still on an affected version.

Regardless, non-retired entries in `sqlth_te` have only cosmetic impact - unless you’re getting to truly ridiculous `_te` record counts (ie, millions) scanning the `_te` table is not going to cause historian performance problems.

---

_[View the full topic](https://forum.inductiveautomation.com/t/what-causes-a-history-tag-to-be-retired/18933)._