# The database connection FAULTED **URL:** \ **Category:** Ignition\ **Tags:** database, ignition79, scripting\ **Created:** [November 4, 2020, 9:29am UTC](https://forum.inductiveautomation.com/t/the-database-connection-faulted/40280 "2020-11-04T09:29:40Z")\ **Posts on this page:** 1\ **Showing post:** 6
**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:** [November 9, 2020, 1:25pm UTC](https://forum.inductiveautomation.com/t/the-database-connection-faulted/40280/6 "2020-11-09T13:25:24Z")
> [@tarun89engg](#): > > ...I/O requests taking longer than 15 seconds to complete on file... I/O requests are a pain in the backside. Use perfmon to monitor the process. > [@Using Perfmon to find bottlenecks in SQL Server](http://forum.inductiveautomation.com/t/using-perfmon-to-find-bottlenecks-in-sql-server/3826): > > The information below is to be used as a guide. Just because the counters collected in your environment may be drastically different from those listed below does not mean that there is a problem. I am sure many of these could be debated but I find the information helpful and you can be the judge if it is useful in your environment(s). I am not the author of the content below so if you see something that you disagree with… don't blame me! slight_smile Memory Bottleneck Analysis Object: - Memo… If this is happening on the same database file I'd add the _SQLServer:Databases:Log Growth_ and _SQLServer:Databases:Log Shrinks_ counters as well. It may be its growth rate is set too low. If the log file is large you may have to set the log type to Simple Transaction (or something like that) and manually shrink it. Some good information here, as well. It turns into a plug for their software, but some good stuff at the top. 😉 --- _[View the full topic](https://forum.inductiveautomation.com/t/the-database-connection-faulted/40280)._