服务依赖问题 [英] service dependency issue

问题描述

我们有一个应用程序服务，具体取决于同一个盒子上的可访问的MSSQL数据库。在MSSQL服务器服务和应用程序服务器之间实现服务依赖性将无济于事，因为在恢复
主数据库时正式启动MSSQL服务 - 而不是在所有数据库都联机时。

我认为我们应该在MSSQL服务的启动参数中有一个选项，以便在"开始"中获取服务。状态，直到所有托管数据库都被恢复。对于单个实例上的许多VLDB，当前行为是有意义的，但不是
1GB数据和整个实例的日志。

好主意？

---

cp

解决方案

你好CP，

尝试将您的应用服务启动类型设置为"自动（延迟启动）"。  自动（延迟）是Windows
Vista中引入的一种新启动类型，它在系统完成启动和初始忙碌操作后不久启动服务

we have an application service depending on a accessible MSSQL database on the same box. Implementing a service dependency between the MSSQL server service and the application server will not help, because the MSSQL service is officially started when the master database is recovered - and not when all databases are online.

I think we should have an option in the startup parameters of the MSSQL service to get the service in the "starting" state until all hosted databases are recovered. For many VLDBs on a single instance the current behavior makes sense, but not for 1GB data and log for the entire instance.

Good idea?

---

cp

解决方案

Hi CP,

Try setting your Application Service startup type as "Automatic (Delayed Start)". Automatic (Delayed) is a new startup type introduced in Windows Vista, that starts the service a short while after the system has finished booting and initial busy operations

这篇关于服务依赖问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！