# Multiple Transaction Groups, One Table

**URL:** <https://forum.inductiveautomation.com/t/multiple-transaction-groups-one-table/117878>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [November 18, 2026, 1:02am UTC](https://forum.inductiveautomation.com/t/multiple-transaction-groups-one-table/117878 "2026-11-18T01:02:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![AIO](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/aio/32/87549_2.png) [@AIO](https://forum.inductiveautomation.com/u/AIO)\
**Post date:** [November 18, 2026, 1:02am UTC](https://forum.inductiveautomation.com/t/multiple-transaction-groups-one-table/117878/1 "2026-11-18T01:02:00Z")

</div>

Hey folks,

Supporting a gateway with many (hundreds) bi-directional transaction groups reading from OPC-UA and writing to the same table on 5-15 second interval. It's been this way for years (10+) and has seemingly worked without issue. After a recent MSSQL upgrade, we're seeing transaction group errors that appear to be associated with deadlock.

My initial reaction is that best practice would to be to condense these writes into a single transaction if able (gateway script & stored procedure), and that these errors are the result of multiple transactions trying to lock a table simultaneously.

Hoping for your thoughts / feedback / best practices. Am I off base? Is there a better solution?

TIA.
