October 30, 2009 at 2:14 pm
We have a SAN that is the location of all our SQL databases. We have one server, for right now, that connects to the SAN where the databases are. This server not only takes a while to boot up, but SQL Server services is set to automatically start and whenever we reboot the machine, the service is not started. I can manually start the SQL Server service and when I look into the SQL log, the initial attempt comes back saying it could not find the database on the G: drive, which is the logical disk of the SAN. Can anyone help?
October 30, 2009 at 2:47 pm
The system must recognize the san before the databases will become available.
You will need to put a dependency on the services such that sql server service does not attempt to start until after the san service is started (san is recognized by the OS).
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
October 30, 2009 at 7:37 pm
I agree. It sounds like SQL is trying to start before either your network connectivity is fully up, or the connection to the SAN is complete. If you have trouble putting a dependancy on the service, you could also set the SQL services to manual and add a startup script that does not start SQL until the SAN becomes available.
Joie Andrew
"Since 1982"
November 3, 2009 at 2:30 pm
This is what I thought but I'm not sure I know what service to make SQL the dependant of. I at first though it would be the iSCSI Initiator but that didn't seem to work. I know this is a SQL forum but any ideas of what service I need to start before I start SQL? I'm running a Dell MD3000i SAN.
unixbomer (10/30/2009)
I agree. It sounds like SQL is trying to start before either your network connectivity is fully up, or the connection to the SAN is complete. If you have trouble putting a dependancy on the service, you could also set the SQL services to manual and add a startup script that does not start SQL until the SAN becomes available.
November 3, 2009 at 2:42 pm
Does the Dell SAN have any software the server uses to connect to it? For instance I know that NetApp tends to have Windows servers use SnapDrive to connect to LUNs off of a SAN volume. So if I was having issues with the database trying to start before the SAN connections were up, I would have the SQL Server service not start until SnapDrive was up. If you look through your system or application log, are there any events that indicate that your SAN connections is up and accepting connections? That would probably tell you what service to run the dependancy off of.
Joie Andrew
"Since 1982"
November 3, 2009 at 3:10 pm
I have to agree with all of this. Talk to your server folks and ask them what they install to support the SAN and then make SQL dependent on it.. That should solve all your problems..
CEWII
November 4, 2009 at 4:25 am
I agree the right way to do this is to make SQL Server dependant on the SAN connectivity service. But if the SAN service reports it is started before it has made all the disks available, or there is no SAN connectivity service, you can tackle the problem in another way.
Open the Windows Service applet and navigate to your SQL Service. Click on the Recovery tab and specify Restart the Service for 'First Failure'. In the 'Restart service after' box, put in enough minutes to allow your SAN disks to connect.
This will not prevent SQL from starting and failing when Windows starts, but it will mean that a few minutes later you have a working SQL service without needing any manual intervention.
You can also set the 'Second Failure' and 'Subsequent Failures' as required for your installation. Personally I always set the 'Reset fail count' to 1 day.
Note that if you use the Recovery tab to restart SQL Server after a failure, you should set the SQL Agent properties so that SQL Agent does not also try to restart the service.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
November 5, 2009 at 8:26 am
This may help for service startup dependency:
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply