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

Re: Generator ThreadPoolSize not having any parallel effect

Subject: Re: Generator ThreadPoolSize not having any parallel effect
From: Joe Webb
Date: Mon, 27 Jun 2005 17:11:00 -0500
Newsgroups: microsoft.public.sqlserver.notificationsvcs
>Can we change the ThreadPoolSize value directly on the database, rather
>than having to nscontrol update changes to it?  We did a
>before-and-after database comparison, and couldn't see any differences
>other than this.

The only supported way to change a configuration is by changing the
ICF and/or ADF and running NSControl update.

HTH...

-- 
Joe Webb
SQL Server MVP


~~~
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)


On 3 Jun 2005 01:27:08 -0700, "ian" <[email protected]>
wrote:

>Thanks Colin,
>
>All our rules are event rules, so the scheduled incompatibility should
>be irrelevant.
>
>We do have sub-quantum ordering enabled. I understand this will mean
>each event batch will have its own row on the NSRuleFirings1 table, but
>would have hoped to see some overlap of the times on these when
>successive rows are for different rule ids within the same quantum.  We
>also tried disabling sub-quantum processing, and this didn't seem to
>help.
>
>Three of our rules are defined as part of the same subscription class.
>Would that affect parallel processing?  Tried moving one to a
>difference class, and it didn't seem to make any difference.
>
>Can we change the ThreadPoolSize value directly on the database, rather
>than having to nscontrol update changes to it?  We did a
>before-and-after database comparison, and couldn't see any differences
>other than this.
>
>Thanks for your patience,
>
>Ian.


<Prev in Thread] Current Thread [Next in Thread>
  • Re: Generator ThreadPoolSize not having any parallel effect, Joe Webb <=