# Transactions (system.db)

**URL:** <https://forum.inductiveautomation.com/t/transactions-system-db/23199>\
**Category:** Ignition\
**Created:** [March 10, 2019, 9:14am UTC](https://forum.inductiveautomation.com/t/transactions-system-db/23199 "2019-03-10T09:14:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![juang](https://avatars.discourse-cdn.com/v4/letter/j/9dc877/32.png) [@juang](https://forum.inductiveautomation.com/u/juang)\
**Post date:** [March 10, 2019, 9:14am UTC](https://forum.inductiveautomation.com/t/transactions-system-db/23199/1 "2019-03-10T09:14:03Z")

</div>

Is there a way for ignition to prevent two transactions from going at the same time.  
example  
two clients make the same exact action(executing a DB transaction, the same transaction) , at the same exact time( I know it’s almost impossible for this to happen) , but if it did happen, is there a way to make ignition give one first , wait for the transaction to be committed, and close and then execute the other one?

---

<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:** [March 10, 2019, 1:12pm UTC](https://forum.inductiveautomation.com/t/transactions-system-db/23199/2 "2019-03-10T13:12:05Z")

</div>

No, but you should be able to constrain the DB to reject the 2nd transaction. Or even better, arrange for those transactions to run from gateway threads where you can interlock them.