mmirtica
Member
I am wondering if any one has any suggestions to gain performance in regards to how JDE connects to SQL Server.
We have roughly 67 users and I’ve noticed that our user connections for SQL Server have been averaging around 378 and have shot up to 415. From what I’ve heard from JDE that it is normal for a user to be connected any where from 4-7 times. It appears that JDE doesn’t reuse connections, but just creates new ones. With that said, we began experiencing IO issues and had to increase our SQL worker threads to compensate with the increase of user connections. This seemed to help, but there has to be a better way to increase the IO with the connections. If JDE is opening a new connection per window, this is a heavy hit on the DB that I would like to avoid if possible. Does anyone have any suggestions around this?
We have roughly 67 users and I’ve noticed that our user connections for SQL Server have been averaging around 378 and have shot up to 415. From what I’ve heard from JDE that it is normal for a user to be connected any where from 4-7 times. It appears that JDE doesn’t reuse connections, but just creates new ones. With that said, we began experiencing IO issues and had to increase our SQL worker threads to compensate with the increase of user connections. This seemed to help, but there has to be a better way to increase the IO with the connections. If JDE is opening a new connection per window, this is a heavy hit on the DB that I would like to avoid if possible. Does anyone have any suggestions around this?