Thank you, Colin. This worked perfectly.
"Colin Meek [MSFT]" <CMeek@online.microsoft.com> wrote in message
news:eIMLiM58EHA.936@TK2MSFTNGP12.phx.gbl...
> You will need to set the <ChronicleQuantumLimit> value as well as the
> <SubscriptionQuantumLimit>. By default, the limit is 1440, which means NS
> will schedule up to 1440 quanta when the service starts up if one or the
> other is not defined.
>
> In your case, susbcriptions will only be processed for the final 2 quanta,
> but chronicle rules will be processed for all 1440. The quanta are
scheduled
> even if there are no chronicle rules to process.
>
> - Colin Meek [MSFT]
>
> --
> 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
>
http://www.microsoft.com/info/cpyright.htm. >
> Please do not send e-mail directly to this alias. This alias is for
> newsgroup purposes only.
> --
>
> "Vince Sefcik" <vsefcik@commserv.ucsb.edu> wrote in message
> news:e3sffs08EHA.3596@TK2MSFTNGP12.phx.gbl...
> > I have both a production server and test workstation that I use for
> > application development. Simply to keep my test workstation from using
> CPU
> > time when not testing an application, I ususally stop the NS instance on
> > that machine. When I start up the NS instance at a later date, SQL
Server
> > runs at 100% CPU utilization for a long time, sometimes up to 15
minutes.
> >
> > I have the following in my ADF:
> >
> > <ApplicationExecutionSettings>
> > <QuantumDuration>PT5S</QuantumDuration>
> > <SubscriptionQuantumLimit>2</SubscriptionQuantumLimit>
> > </ApplicationExecutionSettings>
> >
> > I thought this would limit the number of past Quantums to be processed
> upon
> > instance startup and minimize the load on my test workstation, but it
> > doesn't seem to do so.
> >
> > Can anyone suggest how I can restart an instance and not have it put
such
> a
> > huge load on the machine?
> >
> >
>
>
