microsoft.public.sqlserver.notificationsvcs
[Top] [All Lists]

Deployment Strategy Issue

Subject: Deployment Strategy Issue
From: "RDV"
Date: 30 Aug 2006 05:10:42 -0700
Newsgroups: microsoft.public.sqlserver.notificationsvcs
One deployment strategy is to have the SQLNS instance service (NS$) and
event providers running on one server (A) and the database on another
server (B).  My questions are:

1) How should SQLNS behave when servers A and B are rebooted?  My
experience is that if Server A comes up first and can't connect to the
database it aborts and never starts.

2) How should SQLNS behave when just server B is rebooted?

3) Is there a way to create a service dependence on the instance
service on server A against SQL Server running on server B (e.g create
a service dependence against a process running on another server)?

4) In general are there any best practices for making the above
deployment strategy work when servers are rebooted?


<Prev in Thread] Current Thread [Next in Thread>