# Latent Tag History

**URL:** <https://forum.inductiveautomation.com/t/latent-tag-history/93417>\
**Category:** Ignition\
**Tags:** database, ignition81, perspective\
**Created:** [July 18, 2024, 5:43pm UTC](https://forum.inductiveautomation.com/t/latent-tag-history/93417 "2024-07-18T17:43:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jaron\_Hafso](https://avatars.discourse-cdn.com/v4/letter/j/6de8d8/32.png) [@Jaron\_Hafso](https://forum.inductiveautomation.com/u/Jaron_Hafso)\
**Post date:** [July 18, 2024, 5:43pm UTC](https://forum.inductiveautomation.com/t/latent-tag-history/93417/1 "2024-07-18T17:43:33Z")

</div>

I have noticed odd results when querying Ignition’s “_sqlt\_data\__” tables. I executed a query that selected all records with a “_t\_stamp_” from the previous minute. The number of records remained constant until a few days later when 180 additional records were discovered for the same time period. This caused a 10% increase in records. Is this delay expected or normal behaviour in some cases?

The backfilled records were an assortment of dnp3 devices (majority of connected devices are). No uncharacteristic system events were observed during this time.

Perspective 8.1.41

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [July 18, 2024, 5:52pm UTC](https://forum.inductiveautomation.com/t/latent-tag-history/93417/2 "2024-07-18T17:52:43Z")

</div>

It is normal for any historized tag that uses "analog" deadband style. Which includes "auto" deadband style if the tag datatype is floating point.

> **[Configuring Tag History | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.1/ignition-modules/tag-historian/configuring-tag-history#deadband-and-analog-compression)**
>
> In 8.1.17, the Tag Editor was redesigned to improve usability. The new Tag Editor now requires fewer clicks and keeps relevant tag information visible while modifying bindings, alarms, and event scripts.

Generally, you should not be querying Ignition's data partition tables directly, as you will miss recent information that is being held in memory, awaiting a decision point.