We recently moved our 2017 EPDM professional vault to a new server. The move was to upgrade the server OS and SQL software to the required level when we upgrade to SW 2018. After the move we have had a problem with SQL not starting after the server restarts. I then need to remote into the server and start the SQL service manually even though the service is set to Automatic. I have checked the dependencies for the various SQL services. The only dependency is with the SQL agent, and that seems to be set correctly. Are there any other dependencies I should be looking at? We are running windows server 2012 and SQL server 2014. Also How many of the SQL services should be set to automatic in a normal installation? One other thing that may be relevant is that we went from having the archive server and the database server on separate machines to combining them onto one.
Hi Mark, what account is the SQL service set to start under? If it's a service account (NTSQLSERVER or similar) it may not have enough privileges to start the service since you upgraded the OS. Try changing this to a local system account.