August 24, 2016 at 6:28 am
I'm working on setting up some new servers and one of them is giving me issues with starting the Agent. It looks like, from looking in the SQLAGENT.OUT and ERRORLOGs, that the Agent is trying to start, but the SQL engine isn't ready for connections when it does.
If I go in and manually start the Agent, it starts up with no errors or warnings.
What I'm thinking of doing, but I'm not sure it's a "safe" option, is using the Services MMC (NOT the SQL Configuration Manager) to set the Agent service startup to "Automatic (Delayed Start)" This is not an option in the SCM (I checked.) I've already tried setting a recovery option on the service, which didn't work either (most likely because the service didn't "fail," it stopped itself normally.)
Is it reasonably safe to change the startup type the way I'm looking to do?
Server specs:
Windows Server 2012 R2
SQL Server 2014 SP2
Thanks all,
Jason
August 26, 2016 at 2:15 pm
I don't believe there is much harm in doing this, provided you have no jobs set up to start when SQL Server starts. I would probably look in to whether the SQL Server is slow to start for some reason (is the master database unbelievably huge? msdb taking too long to recover? is tempdb stored on extra slow disks? etc.)
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply