# SQL store one tag, transaction log?

**URL:** <https://forum.inductiveautomation.com/t/sql-store-one-tag-transaction-log/64022>\
**Category:** Ignition\
**Created:** [September 13, 2022, 4:37pm UTC](https://forum.inductiveautomation.com/t/sql-store-one-tag-transaction-log/64022 "2022-09-13T16:37:07Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![Alfredo\_Egmo](https://avatars.discourse-cdn.com/v4/letter/a/ccd318/32.png) [@Alfredo\_Egmo](https://forum.inductiveautomation.com/u/Alfredo_Egmo)\
**Post date:** [September 13, 2022, 7:22pm UTC](https://forum.inductiveautomation.com/t/sql-store-one-tag-transaction-log/64022/8 "2022-09-13T19:22:26Z")

</div>

I found additional information related to this topic if this is helpful for someone.  
Click the Title of the next topic. It has a very detailed comparison of cons/pros

> [@Transaction Groups vs SQLTag Historian](https://forum.inductiveautomation.com/t/transaction-groups-vs-sqltag-historian/5429/2):
>
> That is a good question. There are significant differences between SQLTags historian and transaction groups. SQLTags Historian Pros Data is only logged when the value changes, by exception according to a deadbad Data is compressed using a built-in compression algorithm. An average we see around 54% compression. Data is partitioned into separate tables by month to keep the size of the tables smaller for faster retrieval. Minimal database maintenance Fast retrieval times for large amounts of dat…

---

_[View the full topic](https://forum.inductiveautomation.com/t/sql-store-one-tag-transaction-log/64022)._