# SQL store one tag, transaction log? **URL:** \ **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:** 10\ **Page:** 1
**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, 4:37pm UTC](https://forum.inductiveautomation.com/t/sql-store-one-tag-transaction-log/64022/1 "2022-09-13T16:37:07Z")
I have several tags in my Ignition , I need to store them in SQL but not many tags at the same time in the same transaction, I need to store in SQL one tag at the time (same table), is the recommended way also use transaction groups just to store one tag at the time? or is there another better way? ---
**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:** [September 13, 2022, 4:41pm UTC](https://forum.inductiveautomation.com/t/sql-store-one-tag-transaction-log/64022/2 "2022-09-13T16:41:03Z")
One tag per row, with independent timestamps, is what the standard Tag Historian module does. Just “Enable History” on the tag and set the recording criteria. Multiple tags or values per row, with a common timestamp, is what transaction groups in the SQL Bridge module do. Either approach can be implemented with customizations in scripting. Each approach has pros and cons. What are you trying to do? ---
**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, 4:57pm UTC](https://forum.inductiveautomation.com/t/sql-store-one-tag-transaction-log/64022/3 "2022-09-13T16:57:48Z")
As in the image the idea was to store one tag by row, this is what I am doing now and it is working but of course I have several Std Transaction groups, each with only one tag, this is where my question arise “is this the right way…?” ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/a/4ad70bf5ae895b3f3a943ddaab81028e304994c1.png) ---
**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:** [September 13, 2022, 4:58pm UTC](https://forum.inductiveautomation.com/t/sql-store-one-tag-transaction-log/64022/4 "2022-09-13T16:58:47Z")
No, that is not the right way. Use the historian. ---
**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, 5:13pm UTC](https://forum.inductiveautomation.com/t/sql-store-one-tag-transaction-log/64022/5 "2022-09-13T17:13:04Z")
Is the TAG HISTORIAN an additional module? I don’t see it under my Modules list… ---
**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:** [September 13, 2022, 5:23pm UTC](https://forum.inductiveautomation.com/t/sql-store-one-tag-transaction-log/64022/6 "2022-09-13T17:23:13Z")
Yes. Most users buy it. All of the standard packages from IA include it. ---
**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, 5:30pm UTC](https://forum.inductiveautomation.com/t/sql-store-one-tag-transaction-log/64022/7 "2022-09-13T17:30:43Z")
thank you Sr. ---
**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")
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… ---
**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:** [September 13, 2022, 8:19pm UTC](https://forum.inductiveautomation.com/t/sql-store-one-tag-transaction-log/64022/9 "2022-09-13T20:19:24Z")
Some additional material if you are interested: [https://forum.inductiveautomation.com/search?q=tall%20wide%20table](https://forum.inductiveautomation.com/search?q=tall%20wide%20table) In case it isn’t obvious: the Tag Historian =\> “Tall”, and SQL Bridge transaction groups =\> “Wide”. ---
**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, 8:34pm UTC](https://forum.inductiveautomation.com/t/sql-store-one-tag-transaction-log/64022/10 "2022-09-13T20:34:20Z")
Thank you Sr.