# SQL Server deadlocked

**URL:** <https://forum.inductiveautomation.com/t/sql-server-deadlocked/35685>\
**Category:** Ignition\
**Created:** [June 15, 2020, 11:34pm UTC](https://forum.inductiveautomation.com/t/sql-server-deadlocked/35685 "2020-06-15T23:34:19Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\
**Post date:** [June 16, 2020, 12:11pm UTC](https://forum.inductiveautomation.com/t/sql-server-deadlocked/35685/4 "2020-06-16T12:11:41Z")

</div>

> [@SQL deadlocks on accessing sqlth\_sce](http://forum.inductiveautomation.com/t/sql-deadlocks-on-accessing-sqlth-sce/29717):
>
> We’re expriencing quite some DB errors due to deadlocks in one of our projects (see screenshots below). After executing DBCC TRACEON (1204, -1) on the SQL server, to trace the deadlocks, I was able to get a log from it: [deadlock.log](https://us1.discourse-cdn.com/inductiveautomation/original/2X/0/0890950f345114a497a5a1b6388853a73d2a151c.log) (11.5 KB) It appears that a read and a write to the sqlth\_sce table are causing the issue. But I don’t get when or why the system will use that table. What can we investigate to find the root cause of these errors? This system is running 7.9.11

---

_[View the full topic](https://forum.inductiveautomation.com/t/sql-server-deadlocked/35685)._
