Better Licensing

Question

Better Licensing

Viewing 6 posts - 16 through 20 (of 20 total)

You must be logged in to reply to this topic. Login to reply

Cat-253986 Ten Centuries Points: 1082 More actions · Answer 1

I just wished that there was only one license type. When you work for a large company and everyone is buying licenses, its hard to match up what type of licesenses were purchased for what! Some people buy CALs and some buy per processor - I wish they would all buy per processor. I'm always getting myself confused over how everything is licensed!

Steve Jones - SSC Editor SSC Guru Points: 736478 More actions · Answer 2

It's actually easy. Inside a company, you buy CALs. If the people are authenticated users, Windows Auth, or just AD accounts, they should use CALs. Per processor is for unauthenticated users, primarily Internet ones.

Cat-253986 Ten Centuries Points: 1082 More actions · Answer 3

Steve Jones - Editor (1/2/2008)
It's actually easy. Inside a company, you buy CALs. If the people are authenticated users, Windows Auth, or just AD accounts, they should use CALs. Per processor is for unauthenticated users, primarily Internet ones.

I agree with your point.

I think CALs may be more difficult to manage when you have A LOT of SQL Servers and different users in your environment. Also, you need per processor licenses in a Farm situation.

Lynn Pettis SSC Guru Points: 442467 More actions · Answer 4

Per processor licensing is also valid if you have a large internal user community that is accessing your database. If you purchased SQL Server 2000 or SQL Server 2005 using User CALs, you could spend more than by licensing either per processor. You have to look at how many users may access the system, assuming that it is possible that all may hit the system at the same time (no connurent user licensing with SQL Server).

Meredith Ryan Right there with Babe Points: 749 More actions · Answer 5

Cat (1/2/2008)
I just wished that there was only one license type. When you work for a large company and everyone is buying licenses, its hard to match up what type of licesenses were purchased for what! Some people buy CALs and some buy per processor - I wish they would all buy per processor. I'm always getting myself confused over how everything is licensed!

The only way to ensure that you in compliance all the time is to have one person (or a team of a few people) that purchase all licensing for the company. We were completely out of whack licensing wise until we changed our process. At this point, we're small enough (between 400-500 associates) that if an invoice for software goes to our payables team and I haven't signed off on it, AP doesn't pay it until I have all the details, and say okay. Its the only way to ensure that your licensing is compliant and that you can prove compliancy. That proof is almost as important as the compliancy itself.

Meredith Ryan Right there with Babe Points: 749 More actions · Answer 6

I think CALs may be more difficult to manage when you have A LOT of SQL Servers and different users in your environment. Also, you need per processor licenses in a Farm situation.

What do you mean by a Farm situation?

The only time I am aware of needing per proc licenses is when you cannot identify the number of devices or users that will be accessing your SQL servers... ie: a DB on the outside of your DMZ.