• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

SQL Server 2000 lisencing

KAMAZON

KAMAZON

Golden Member
Hello, I work for a large corporation that is auditing their SQL lisences for a upgrade to 2005. They are slightly confused about their lisencing model and are curious if it was changed. They asked me to find out if SQL Server 2000 will block connections if you don't have enough CALs for all of your connections. Does anyone know? I haven't been able to find this out anywhere. Thank you.
 
I'm not totally sure about this but this is how I understand it to work. If you have 5 SQL CAL's then you would only be able to have 5 concurrent connections. As a connection opens up, someone else can connect. Whether or not SQL will actually allow more than 5 I don't know. If you need unlimited connections then you need to go with the "per processor" license scheme for SQL Server.
Again, this is just my interpretation and I may be way off base on this.
 
Thanks for the post ITJunkie, and I have the same understanding as you on this matter. We are currently using 'per processor' on many servers, but for some reason, the DBA wants to know what happens if we reach the limit of our lisences.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top