Folks,
I have read the SQL Notification Services Documentation, but as I am a novice
with SQL NS, I was hoping for clarification on a couple of application settings.
I am using an app written for SQL 2000 NS (it's called the Notification Workflow
Solution Accelerator). I a few mostly yes/no questions below. Any info is
greatly appreciated.
Here are the settings I have questions about in the AppADF.xml file
<ApplicationExecutionSettings>
<QuantumDuration>PT15S</QuantumDuration>
<SubscriptionQuantumLimit>0</SubscriptionQuantumLimit>
<ChronicleQuantumLimit>0</ChronicleQuantumLimit>
</ApplicationExecutionSettings>
I see this definition in the SQL NS Documentation below.
SubscriptionQuantumLimit - Specifies how far the logical (quantum) clock
can fall behind the real-time clock before skipping subscription rule firings.
The documentation also goes on to say that the default is 30 minutes given
a quanta duration of 1 minute.
Questions:
In plain english, does that mean that if the application is 30 quanta behind,
it would skip processing the oldest pending items?
What would the default value then be given a QuantumDuration of 15 seconds?
What is the value when SubscriptionQuantumLimit is set to 0?
I also see this definition in the SQL NS Documentation below.
ChronicleQuantumLimit - Specifies how far the logical (quantum) clock can
fall behind the real-time clock before skipping event chronicle rule firings.
The documentation also goes on to say that the default is 1,440 quanta, which
is 1,440 minutes or 1 day, assuming a default QuantumDuration value of 1
minute.
Questions:
In plain english, does that mean that if the application is 1440 quanta behind
(given a quantum of 1 minute), it would skip processing the oldest pending
items?
Would the default, given a quantam duration of 15 seconds, then be only one
quarter of 1440?
And 0 is a special value that means skip nothing (process all no matter what)?
Regards,
Pete Zerger, MCSE(Messaging), MVP - MOM
Co-founder and Webmaster, MOMResources.org
URL:http://www.momresources.org
BLOG: http://www.it-jedi.net/
mailto:pete.zerger AT gmail.com
...or find me in the forums at http://momcommunity.com
Joe Webb - 28 Aug 2006 12:35 GMT
Hi Pete -
>In plain english, does that mean that if the application is 30 quanta behind,
>it would skip processing the oldest pending items?
>What would the default value then be given a QuantumDuration of 15 seconds?
>What is the value when SubscriptionQuantumLimit is set to 0?
Let's say the system goes down for some reason - you take it off line
for scheduled maintenance or there's a significant hardward failure.
When the system comes back up, it's going to attempt to catch up on
all of the quantums it missed while it was down.
The QuantumLimit tells the system to not go back further than that
point. So if the QuantumLimit is 10, and you've been down for 100
quantums (regardless of what the duration is) it'll only go back and
process the most recent 10 quantums.
Setting the value to 0 tells the system to start processing from it's
last quantum regardless of how far behind it is. Sometimes this is
very important, other times not so much.
The QuantumDuration defines how long a quantum is, that is to say, how
often the generator looks for new batches to process.
The difference in ChronicleQuantumLimit and SubscriptionQuantumLimit
is that the former affects scheduled rule processing while the latter
affects event-driven rule processing.
HTH...

Signature
Joe Webb
SQL Server MVP
http://www.sqlns.com
~~~
Get up to speed quickly with SQLNS
http://www.amazon.com/exec/obidos/tg/detail/-/0972688811
I support PASS, the Professional Association for SQL Server.
(www.sqlpass.org)
>Folks,
>
[quoted text clipped - 48 lines]
>
>...or find me in the forums at http://momcommunity.com
Pete Zerger - 15 Sep 2006 04:44 GMT
Hello Joe,
Thanks again Joe.
Regards,
Pete Zerger, MCSE(Messaging), MVP - MOM
URL:http://www.momresources.org
BLOG: http://www.it-jedi.net/
> Hi Pete -
>
[quoted text clipped - 87 lines]
>> mailto:pete.zerger AT gmail.com
>> ...or find me in the forums at http://momcommunity.com