# Store and Read exact data from Historian

**URL:** <https://forum.inductiveautomation.com/t/store-and-read-exact-data-from-historian/113581>\
**Category:** Ignition\
**Created:** [January 27, 2026, 10:32pm UTC](https://forum.inductiveautomation.com/t/store-and-read-exact-data-from-historian/113581 "2026-01-27T22:32:05Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Eugene49](https://avatars.discourse-cdn.com/v4/letter/e/c6cbf5/32.png) [@Eugene49](https://forum.inductiveautomation.com/u/Eugene49)\
**Post date:** [January 27, 2026, 10:32pm UTC](https://forum.inductiveautomation.com/t/store-and-read-exact-data-from-historian/113581/1 "2026-01-27T22:32:05Z")

</div>

I have a data acquisition application, using transaction group, is not really so efficient, so looking back at historizing tag.

Say that I have two ignition tag, which data comes from two pressure sensors.  
For testing application, on data change, I want Ignition to record exact data into historian  
When being query on perspective, i need exact data as stored to be read. (I understood that on reading these data, ignition may perform operation on the data if desired.)

Regardless of tag history setting (deadband style, etc).  
Does Ignition store data in historian exactly as what the data at that moment?

Background:  
I have setup transaction group to record 40 sensors when triggered.

1. On transaction group trigger, we record each data from 40 sensors, data have changed or not.  
(thus not storage efficient..?)
2. When charting, chart component will crash because of so many data

---

<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:** [January 27, 2026, 11:22pm UTC](https://forum.inductiveautomation.com/t/store-and-read-exact-data-from-historian/113581/2 "2026-01-27T23:22:21Z")

</div>

The tag historian does **not** synchronize storage of multiple tags. Each tag is solo, and recorded separately.

If you need multiple tag values recorded together, then SQL Bridge transaction groups are the right tool, or you can script an SQL insert.

---

<div class="post-metadata">

**Author:** ![Eugene49](https://avatars.discourse-cdn.com/v4/letter/e/c6cbf5/32.png) [@Eugene49](https://forum.inductiveautomation.com/u/Eugene49)\
**Post date:** [January 27, 2026, 11:49pm UTC](https://forum.inductiveautomation.com/t/store-and-read-exact-data-from-historian/113581/3 "2026-01-27T23:49:29Z")

</div>

> [@pturmel](#):
>
> The tag historian does **not** synchronize storage of multiple tags. Each tag is solo, and recorded separately.

Yes, but I can query multiple tag history by using `queryTagHistory` with wide format? yeah?

> [@pturmel](#):
>
> If you need multiple tag values recorded together, then SQL Bridge transaction groups are the right tool, or you can script an SQL insert.

Instead of this, was thinking, during measurement, get the startDatetime and endDatetime, then use `queryTagHistory`, wouldn’t this work as well?

---

<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:** [January 27, 2026, 11:58pm UTC](https://forum.inductiveautomation.com/t/store-and-read-exact-data-from-historian/113581/4 "2026-01-27T23:58:40Z")

</div>

> [@Eugene49](#):
>
> wide format

You should experiment. I doubt you'll like this.

> [@Eugene49](#):
>
> get the startDatetime and endDatetime

Good luck.