|
|
Posted by David Portas on 03/22/06 13:15
mleal wrote:
> Hi Dan. Thanks for answering.
>
> But I cannot use processor licensing for all these applications and the
> other ones we have here.
> Believe me, it would increase the costs a lot.
>
> Try to imagine almost 1000 databases. How do I know that I have the
> CALs that I need?
>
> It's a very complicated problem.
>
>
> Regards,
> Marcio
The point is that SQL Server CALs are licensed per end user not per
connection. So regardless of the method used to connect SQL Server
can't count the number of users for you. The number of databases is
also irrelevent.
With Enterprise Edition, Processor Licensing is cheaper unless you have
fewer than about 100 users per processor. About half that number for
Standard Edition. So if your user base is that small you shouldn't have
so much trouble tracking the number of licences required. How many
users do you have?
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--
Navigation:
[Reply to this message]
|