# Database \[mysql\] timeout

**URL:** <https://forum.inductiveautomation.com/t/database-mysql-timeout/34238>\
**Category:** Ignition\
**Tags:** ignition79\
**Created:** [April 27, 2020, 3:10pm UTC](https://forum.inductiveautomation.com/t/database-mysql-timeout/34238 "2020-04-27T15:10:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![daniel.garcia-redrue](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/daniel.garcia-redrue/32/10258_2.png) [@daniel.garcia-redrue](https://forum.inductiveautomation.com/u/daniel.garcia-redrue)\
**Post date:** [April 27, 2020, 3:10pm UTC](https://forum.inductiveautomation.com/t/database-mysql-timeout/34238/1 "2020-04-27T15:10:55Z")

</div>

Hi all,  
I’m working on a transaction group that calls a stored procedure defined on my database. This procedure deletes old records in a huge table and it takes a lot of time (called for example from SQLYog it takes around 4 minutes to finish). This long execution causes a read timeout in ignition after 120,001 ms (com.mysql.jdbc.exceptions.jdbc4.CommunicationsException).

I tried to update Read Timeout and OPC Browse timeout in the project properties, but nothing changed.

Any idea?

Thanks in advance

---

<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:** [April 27, 2020, 3:39pm UTC](https://forum.inductiveautomation.com/t/database-mysql-timeout/34238/2 "2020-04-27T15:39:05Z")

</div>

Take a look at the “socketTimeout” extra connection property. Even better, modify your process to delete smaller chunks more often.