>If you have a dependency i.e. your SQL databases are on a vdisk, then yes, the disk has to be up and available before you try to start SQL Server.
>
>Another general approach would be to use a batch/CMD file or PowerShell script to start the vdisk, then SQL Server.
>
>In Services: Set SQL Server to manual (rather than automatic) start in Services
>
>In the script:
>
>- Start the vdisk
>
>- Go into a loop, checking for the existence of one of the SQL database files. If file does not exist (i.e. vdisk hasn't finished starting up), keep looping
>
>- Once the file exists, start SQL Server:
https://technet.microsoft.com/en-us/library/ms187598%28v=sql.105%29.aspxInteresting, thanks
