MS SQL 2000 licensing

[rtierney]

This may be the wrong forum for this, but I thought I'd try anyway.

Basically, we need to purchase a copy of SQL Server 2000 for a client. Over 200 different people will be using it off and on once it's installed. I've only been able to find 1-processor licenses (with unlimited connections) or 5/25 CAL licenses.
The database server they'll be using is a dual processor machine, so the single processor option is out the window, but I'd think we'd need much more than the 25-CAL option.
Is it possible to buy a two processor license? I haven't seen any anywhere. Or would it be possible to buy two single processor packages and use both together?

I'm just unsure which specific licensing option to go with.
Anyone have any expertise in this?

[MorfiusX]

Yes, you can buy a multiprocessor license. Call up a software vendor and get a quote. Dell, IBM, CDW, etc. will all be more than willing to quote you.

You can buy a single proc license for a dual proc server. SQL 2000 has the option to customize the number of processors it uses.

Also, it goes by physical chips. So, a dual core chip still counts as one proc for licensing.

The last time I got a quote, the MS rep said they have a formula for calculating which option, proc licensing or CALs, will be the cheapest. If I remember correctly, 1 proc license equals about 500 CALs. But, the vendor will be able to answer that for sure.

[rtierney]

Yes, you can buy a multiprocessor license. Call up a software vendor and get a quote. Dell, IBM, CDW, etc. will all be more than willing to quote you.

You can buy a single proc license for a dual proc server. SQL 2000 has the option to customize the number of processors it uses.

Also, it goes by physical chips. So, a dual core chip still counts as one proc for licensing.

They'll want to use both physical processors.
I'll give CDW a shot tomorrow.

Thanks for the help.

[hulksterjoe]

If you've got a dual proc system you just buy 2 of the single proc unlimited user licenses and your all set...They aint cheap.. pn# is 228-01079

[big daddy fatsacks]

now wait a minute. CALs and per-processor licensing are 2 different things. licensing it for 2 processors is insanely expensive, but is unnecessary if you choose not to license it by processor. instead you can license it by CALs. per-device or per-user.

see here: http://www.developer.com/db/article.php/3502746

i also suggest you go to the MS site and read whatever they have regarding SQL server licensing before you spend a dime.

[hulksterjoe]

The cost of an sql cal thru open licensing is about $150each.. while that per proc license will cost you around $4500 or so... plus dont forget you still need to buy the server license regardless at around $850.. so just do the math.. you said 200 people ..on and off . this is also when you should decide which type of license you want if you go the CAL route either per user or per device....

In case your not familiar.. per user will allow 1 user to connect from unlimited devices ie; computer-notebook-pda- etc etc.. while per device will allow unlimited users to connect from 1 device. this is perfect for a call center or warehouse where 3 shifts use the same computer...If you go per proc then it wont matter..

but If we say you need 100 cals for shits.. then 150x100 = $15000.... so the per proc route at 9k or 10k is a far better route in that case

[rtierney]

The amount of users connecting to the database will need to grow over time, so I'm thinking a per-processor license is best.

So if I contact a vendor, I'll be able to get a quote on a dual-processor license?

[DougLite]

I stand corrected. Nothing to see here folks.

[SJConsultant]

IIRC, the licensing model for SQL is different than Server product licensing. I'm wanting to say that you pay per thread on SQL, not per CPU socket like you do for Server OSes.

SQL 2005 licensing (http://www.microsoft.com/sql/howtobuy/default.mspx) is per processor, per user, or per device.

SQL 2005 has "downgrade" rights so I would look to purchase an '05 license with the intent to upgrade at a later date when the application is supported.

[figgie]

IIRC, the licensing model for SQL is different than Server product licensing. I'm wanting to say that you pay per thread on SQL, not per CPU socket like you do for Server OSes.


Per thread...

Not oracle ;)

MS SQL is real basic for licensing. Of course the license themselves can be very confusing but here

right from Microsoft (http://www.microsoft.com/sql/howtobuy/default.mspx)

SQL Server is available under three licensing options:

• Processor Licensing Model. Under this model, a license is required for each physical or virtual processor accessed by an operating system environment running SQL Server. This license does not require any device or user client access licenses (CALs).

• Server plus Device CALs. Under this model, a server license is required for each operating system environment running an instance of SQL Server, as well as a CAL for each client device that accesses a system running SQL Server.

• Server plus User CALs. Under this model, a server license is required for each operating system environment running an instance of SQL Server, as well as a CAL for each user that accesses a system running SQL Server.

ninjaedit:

doh SJ beat me to it :)