Originally Posted by
StuckInYYZ
Trust me. Had an issue that happened with a few clients where if a server was configured in a certain way, after about a week or so, a server would go offline due to resource exhaustion. There were two fixes. First was a reboot (which you can't keep doing weekly in a production environment).
Actually.... our main office used to reboot their servers on Fridays at 12 noon. All of them. I thought it was ridiculous. Fortunately we only used their systems for time & billing. As you might expect, there were quite a few times when everyone got sent home by 2pm when a server decided not to come back up and it wasn't going to be an easy fix. They didn't have any redundancy either. ::facepalm::
Oddly enough, they split the company and we inherited the time & billing system, but no hardware to run it on. It was a mess. the DB and tables all were fragmented 85-98%. Nothing was documented. I cleaned it up and shoehorned it into a Win10 (updates disabled) XCP-NG VM running MS SQL Express and it's been well-behaved. Not a single reboot in 20 months. Performance, even on a circ-2007 Dell 2950, VM'd, is light years faster than when they had it. Snappy, actually. Even the worst report takes <2 seconds to complete. I'm not sure if it's incompetence or all of the overhead of a full MS server + full MS SQL, although I have my suspicions.