Not sure whether this will apply to you or not, but I recently had a client running an ERP for hundreds of client databases spread over multiple servers. We became aware of problem they were having with random timeouts to a specific server. Since all our other server connections were working fine (ie: never timing out), I suggested they check the network card, network cable & network port on the switch. After some testing, they ended up changing out the network card and the problem went away. Our assumption was we were getting early warning signs of an impending network card failure. This occurred almost a year ago and we've had no timeouts since then.
This may not be the issue since you are running on a single server, but stranger things have happened. Hope this helps!
Paul H. Tarver
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of M Jarvis Sent: Friday, July 13, 2018 1:26 PM To: profoxtech@leafe.com Subject: [NF] SQL Server - too many databases?
We are running into an intermittent issue w/ our SQL Server running SQL2016. It's not that our tables are all that large (usually), but our server is trying to manage around 550 different DB's parked on it. Few of the DB's are open at any one time, but the server has to keep track of them at least to some extent.
When the problem arises our dev team runs into timeouts and sometimes the problem goes away, some time it doesn't and our IT guys out of desperation restarts the machine.
One of our devs suggested that even though we aren't past some theoretical limit on the number of DB's the server can manage, maybe we just have too many and getting rid of most, or at least detaching them, might help.
Any thoughts on this?