<div>
<div class="content wysiwyg-content">
I have a Service that uses MS SQL Server as a backend to serve up a database of digital assets.<br />
When the computer is restarted, it seems that sometimes this service starts up before MS SQL Server, cannot find the necessary databases and then is does not serve them up properly.<br />
<br />
Now it seems that there is a way that a Service can have Dependencies and that would be just what I need to ensure that the Service starts up AFTER MS SQL Server. However, there seems to be no way to set this in the Services Control Panel.<br />
<br />
How can I make sure that this Service does not start until MS SQL Server has completely started?<br />

</div>
</div>


I have a Service that uses MS SQL Server as a backend to serve up a database of digital assets.
When the computer is restarted, it seems that sometimes this service starts up before MS SQL Server, cannot find the necessary databases and then is does not serve them up properly.

Now it seems that there is a way that a Service can have Dependencies and that would be just what I need to ensure that the Service starts up AFTER MS SQL Server. However, there seems to be no way to set this in the Services Control Panel.

How can I make sure that this Service does not start until MS SQL Server has completely started?


Setting Dependencies (or startup order) for Services

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).