Re: Licensing question for NS
I know you've received the answer to this question offline, but for
the benefit of those following the thread or searching for an answer
in the future...
For SQLNS 2005, you need a licensed copy of SQL Server for each
computer on which a SQLNS component runs. For example in the Remote
Database Deployment scenario, you'll need 2 SQL Server licenses. The
computer that hosts the Subscription Management Application does not
require a SQL Server license; it can use the client redistribution
This licensing agreement differs from the prior version in which the
Remote Database Deployment Scenario did not require a separate SQL
Thanks Lukasz for clarifying this offline!
SQL Server MVP
Get up to speed quickly with SQLNS
I support PASS, the Professional Association for SQL Server.
On Wed, 26 Apr 2006 05:19:02 -0700, CB <[email protected]>
>My question is: in a scale out deployment, where the NS database will sit on
>an existing (and already-paid-for) clustered instance of SQL Enterprise
>edition 2005, and the distributor/generator Windows service (the NS engine)
>sits on a separate server with no SQL on it - does this scale-out force us to
>purchase another license for SQL for the generator/distributor machine? Or
>since we're accessing the resources of the already-paid-for instance, does
>that take care of it? I found this on Microsoft's site, but the other Q&A on
>the NS site is a little unclear....
>"You may install and use Notification Services or any of its component on
>computers that are not running SQL Server provided that they are accessing
>the services of the computer that is running SQL Server under the Per
>Processor licensing model"
|<Prev in Thread]
||[Next in Thread>|
- Re: Licensing question for NS,
Joe Webb <=