Number of per seat Licences configured in sql server.

Hi, I have a server running windows 2000 server sp4, sql server 2000
sp3. When i installed the sql server software i Configured a 500 per
seat licences.
this week i check that the sql server is running about 578 concurrent
users, so my question is.
Is the server performance affected in this situation'
Do I have to configure more licences to let the server runs better than
now'
doesn´t it matter if I change the quantity of licences on the server'
Thanks a lot for your help.
*** Sent via Developersdex http://www.developersdex.com ***MariaGuzman wrote:
> Hi, I have a server running windows 2000 server sp4, sql server 2000
> sp3. When i installed the sql server software i Configured a 500 per
> seat licences.
> this week i check that the sql server is running about 578 concurrent
> users, so my question is.
> Is the server performance affected in this situation'
> Do I have to configure more licences to let the server runs better than
> now'
> doesn=B4t it matter if I change the quantity of licences on the server'
> Thanks a lot for your help.
>
>
> *** Sent via Developersdex http://www.developersdex.com ***
The number of configured licences has no affect on performance.
SQL Server is licensed either Per Processor or Per CAL. Under CAL
licensing the licence agreement requires that you purchase a CAL for
each end user or client device. The number of concurrent users is
irrelevant (in fact SQL Server can't even tell you the number of
concurrent users - it only knows about the number of concurrent
*connections*, which may be more or may be less than the total number
of users or devices).
You should check this out for yourself at the licensing site but if you
have 500 users and just this one server then you will almost certainly
find it cheaper to buy processor licences instead of CALs.
http://www.microsoft.com/sql/howtobuy/default.mspx
--
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
--