[Top] [All Lists]

Re: Restarting NS$AppName service?

Subject: Re: Restarting NS$AppName service?
From: "Shyam Pather [MSFT]"
Date: Thu, 7 Jul 2005 11:09:13 -0700
Newsgroups: microsoft.public.sqlserver.notificationsvcs
In addition to what Joe say's below, you can also define an expiration age 
for notifications. If notifications are generated, but not delivered due to 
the service being down, the expiration age determines whether the 
distributor will pick them up and deliver them when the service is 
restarted. Notifications older than the expiration age will be discarded, 
those newer will be delivered as normal.

To be clear, the settings Joe mentions deal with the processing of old 
events to generate notifications; the notification expiration age deals with 
the processing of old notifications that have already been generated.

BTW, the name of the service is NS$[InstanceName], not NS$[AppName].

Learn more about SQL-NS:
This posting is provided "AS IS" with no warranties, and confers no rights. 
Use of included script samples are subject to the terms specified at
"Joe Webb" <[email protected]> wrote in message 
news:[email protected]
> Hi Scott -
> Yes. When you restart a stopped NS instance, it'll attempt to catch up
> on anything it's missed while stopped.
> Check out the <SubscriptionQuantumLimit> Element and
> <ChronicleQuantumLimit> Element in the <ApplicationExecutionSettings>
> node of the ADF in BOL for details on how to configure the amount of
> time (specified in the the number of quantas behind the current
> quantum) it'll go back to catch up. The default is 30 quanta with each
> quantum being 1 minute by default.
> HTH....
> -- 
> Joe Webb
> SQL Server MVP
> ~~~
> Get up to speed quickly with SQLNS
> I support PASS, the Professional Association for SQL Server.
> (
> On Thu, 7 Jul 2005 09:47:02 -0600, Scott <[email protected]> wrote:
>>Hi, and thanks for your followup to my "NotificationsDeliveryNotAttempted"
>>post the other day.
>>If the NS$[AppName] service was stopped for a time and then restarted, 
>>it pickup any events that were submitted during the down time?  And if so,
>>is there some kind of a timeout setting where events would be too old to 
>>picked up and would be ignored?  I didn't see anything in the docs on this
>>topic.  Right now this is more of a curiosity question, but in the future
>>the way that NS handles service restarts does have some real implications.

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