# SQL Express Database Question

**URL:** <https://forum.inductiveautomation.com/t/sql-express-database-question/27156>\
**Category:** General Discussion\
**Created:** [August 5, 2019, 12:05pm UTC](https://forum.inductiveautomation.com/t/sql-express-database-question/27156 "2019-08-05T12:05:32Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![grietveld](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/grietveld/32/6984_2.png) [@grietveld](https://forum.inductiveautomation.com/u/grietveld)\
**Post date:** [August 5, 2019, 12:05pm UTC](https://forum.inductiveautomation.com/t/sql-express-database-question/27156/1 "2019-08-05T12:05:32Z")

</div>

I’m not the strongest DB guy, especially in SQL, but figured I might be able to get some help here.

I’ve got an SQL Express instance running side by side with Ignition on a development computer. Once we have a few transactions executing around the same time, the database ends up having processes get suspended in waiting for another task. These tasks seem to range from stored procs, to named queries, all of which are fairly simple.

Any ideas of where I should start to look to resolve this issue?

---

<div class="post-metadata">

**Author:** ![mvanryn](https://avatars.discourse-cdn.com/v4/letter/m/ea666f/32.png) [@mvanryn](https://forum.inductiveautomation.com/u/mvanryn)\
**Post date:** [August 6, 2019, 7:37pm UTC](https://forum.inductiveautomation.com/t/sql-express-database-question/27156/2 "2019-08-06T19:37:34Z")

</div>

What is the CPU and memory usage of the process? Are you up against the 1 GB RAM limit?

---

<div class="post-metadata">

**Author:** ![grietveld](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/grietveld/32/6984_2.png) [@grietveld](https://forum.inductiveautomation.com/u/grietveld)\
**Post date:** [August 6, 2019, 7:40pm UTC](https://forum.inductiveautomation.com/t/sql-express-database-question/27156/3 "2019-08-06T19:40:22Z")

</div>

I think we may have figured it out. We were pretty low on CPU and memory usage.

I think the issue was related to some Transactions called in our Stored procedure causing some havoc. So far today, things have been smooth, so hopefully after a bit more testing we can confirm the issue is resolved.