November 24, 2010 at 6:54 am
Hi
I am trying to understand what the best SQL Server 2008 R2 licensing would be for our organisation. This licenses would need to cover a Sharepoint implementation that would be used by an unknown amount of external users.
If I was to take the server\CAL approach do external users in this case each need a CAL? Or is this covered by a device CAL of the web front end that the users connect to?
Also how are service accounts that connect from the application to the SQL Server seen, do they also need a CAL?
Then there is the support staff, whom I assume would also need a CAL each.
The simpler approach seems to be the per processor license however I am weighing up my options.
Thanks for any pointers
November 24, 2010 at 6:55 am
Per-processor is how most multi-user installations are done. CALs are mostly useful to very small shops with a small number of people accessing the system.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
November 24, 2010 at 6:58 am
So in Microsoft language a user is someone using an application with a SQL backend and not someone who access the SQL instance directly e.g. a DBA.
November 24, 2010 at 6:58 am
Each user would need a CAL. If you don't know how many users there will be (normal for a web implementation) then you need to go per-processor.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 24, 2010 at 7:01 am
GSquared (11/24/2010)
Per-processor is how most multi-user installations are done. CALs are mostly useful to very small shops with a small number of people accessing the system.
Sorry to highjack this thread, but assuming a web environement on a virtual server (4 procs), based on a physical server with 2 cpus / quad core.
Am I correct in assuming that only 1 proc license is required for that virtual server?
And then what about 5+ cores on the virtual server?
November 24, 2010 at 7:03 am
Ninja's_RGR'us (11/24/2010)
GSquared (11/24/2010)
Per-processor is how most multi-user installations are done. CALs are mostly useful to very small shops with a small number of people accessing the system.Sorry to highjack this thread, but assuming a web environement on a virtual server (4 procs), based on a physical server with 2 cpus / quad core.
Am I correct in assuming that only 1 proc license is required for that virtual server?
And then what about 5+ cores on the virtual server?
1 license per physical CPU. http://www.microsoft.com/sqlserver/2008/en/us/licensing-faq.aspx
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
November 24, 2010 at 7:11 am
Thats great guys thanks for the help again 🙂
November 24, 2010 at 7:33 am
Ok I have got myself in a tiz about device CALs now!!
How does a web front end not qualify for a device CAL when all external users will be going via this server to access the application?
Furthermore do service accounts that the application uses need CALs?
I ask as we have a small internal application for a limited number of users that will need licensing.
Thanks
November 24, 2010 at 8:08 am
GSquared (11/24/2010)
Ninja's_RGR'us (11/24/2010)
GSquared (11/24/2010)
Per-processor is how most multi-user installations are done. CALs are mostly useful to very small shops with a small number of people accessing the system.Sorry to highjack this thread, but assuming a web environement on a virtual server (4 procs), based on a physical server with 2 cpus / quad core.
Am I correct in assuming that only 1 proc license is required for that virtual server?
And then what about 5+ cores on the virtual server?
1 license per physical CPU. http://www.microsoft.com/sqlserver/2008/en/us/licensing-faq.aspx
be careful there. In an ESX server, SQL see a core as a CPU. So, on a 2 CPU ESX server, each CPU having 6 cores, SQL would see that as 12 cpus if the VM was built that way.
microsoft has altered the license agreement for virtual enviroments also....
Now, with SQL 2008 R2, you would buy for the number of CPU's the ESX host has, then you are allowed to install it up to 4 times on that ESX server. for EE edition only.
so we have several esx farms, each having 2 cpu (12 total cores) and we install SQL 2008 R2 EE 4 times per server and give as many cores (CPU's) as needed.
November 24, 2010 at 8:41 am
Kwisatz78 (11/24/2010)
Ok I have got myself in a tiz about device CALs now!!How does a web front end not qualify for a device CAL when all external users will be going via this server to access the application?
Furthermore do service accounts that the application uses need CALs?
I ask as we have a small internal application for a limited number of users that will need licensing.
Thanks
Simply put, you could have 1 000 000 distinct users all buying the same ticket to see a concert... it just doesn't make sens that way.
November 24, 2010 at 8:52 am
Geoff A (11/24/2010)
GSquared (11/24/2010)
Ninja's_RGR'us (11/24/2010)
GSquared (11/24/2010)
Per-processor is how most multi-user installations are done. CALs are mostly useful to very small shops with a small number of people accessing the system.Sorry to highjack this thread, but assuming a web environement on a virtual server (4 procs), based on a physical server with 2 cpus / quad core.
Am I correct in assuming that only 1 proc license is required for that virtual server?
And then what about 5+ cores on the virtual server?
1 license per physical CPU. http://www.microsoft.com/sqlserver/2008/en/us/licensing-faq.aspx
be careful there. In an ESX server, SQL see a core as a CPU. So, on a 2 CPU ESX server, each CPU having 6 cores, SQL would see that as 12 cpus if the VM was built that way.
microsoft has altered the license agreement for virtual enviroments also....
Now, with SQL 2008 R2, you would buy for the number of CPU's the ESX host has, then you are allowed to install it up to 4 times on that ESX server. for EE edition only.
so we have several esx farms, each having 2 cpu (12 total cores) and we install SQL 2008 R2 EE 4 times per server and give as many cores (CPU's) as needed.
Thanks for all the info. However I can't make heads or tales about it.
I know very little about VM and the sys admin is a rookie at best. I'm trying to find out wether we have the right licenses for our setup.
Here's what I know for sure :
The physical machine has 2 physical xeon proc quad core.
In the VM setup environement, the sys admin has given 4 processors to the SQL VM, which in theory actually means 4 cores from 1 physical CPU.
We are running on windows server 2008 64 Bit
SQL Server standard 64 Bit.
The current license is way under our current use (100s of web user, but the license is for 5 cals). The sysadmin was badly advised by a D**l csr and I'm trying to straighten out the situation.
TIA for any clarifications on what we need.
November 30, 2010 at 6:30 am
Ninja's_RGR'us (11/24/2010)
Geoff A (11/24/2010)
GSquared (11/24/2010)
Ninja's_RGR'us (11/24/2010)
GSquared (11/24/2010)
Per-processor is how most multi-user installations are done. CALs are mostly useful to very small shops with a small number of people accessing the system.Sorry to highjack this thread, but assuming a web environement on a virtual server (4 procs), based on a physical server with 2 cpus / quad core.
Am I correct in assuming that only 1 proc license is required for that virtual server?
And then what about 5+ cores on the virtual server?
1 license per physical CPU. http://www.microsoft.com/sqlserver/2008/en/us/licensing-faq.aspx
be careful there. In an ESX server, SQL see a core as a CPU. So, on a 2 CPU ESX server, each CPU having 6 cores, SQL would see that as 12 cpus if the VM was built that way.
microsoft has altered the license agreement for virtual enviroments also....
Now, with SQL 2008 R2, you would buy for the number of CPU's the ESX host has, then you are allowed to install it up to 4 times on that ESX server. for EE edition only.
so we have several esx farms, each having 2 cpu (12 total cores) and we install SQL 2008 R2 EE 4 times per server and give as many cores (CPU's) as needed.
Thanks for all the info. However I can't make heads or tales about it.
I know very little about VM and the sys admin is a rookie at best. I'm trying to find out wether we have the right licenses for our setup.
Here's what I know for sure :
The physical machine has 2 physical xeon proc quad core.
In the VM setup environement, the sys admin has given 4 processors to the SQL VM, which in theory actually means 4 cores from 1 physical CPU.
We are running on windows server 2008 64 Bit
SQL Server standard 64 Bit.
The current license is way under our current use (100s of web user, but the license is for 5 cals). The sysadmin was badly advised by a D**l csr and I'm trying to straighten out the situation.
TIA for any clarifications on what we need.
What edition of SQL Server? If it's Enterprise, and you're limiting the VM to one physical CPU (one slot on the motherboard), you need 1 CPU license.
If the VM can access the second physical CPU, you'll need 2 licenses.
You can always e-mail Microsoft customer support to verify any licensing questions. That'll get you answers "straight from the horse's mouth" as it were, but the FAQ I posted a link to earlier has all the data on physical CPUs.
If it's not Enterprise Edition, you'll need to check the FAQ or contact Microsoft. I think Standard works the same way, but I wouldn't swear to it.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
November 30, 2010 at 6:33 am
Thanks for the help GSquared... it's on standard.
I'll give MS a ring when I have a chance.
December 1, 2010 at 8:45 am
Kwisatz78 (11/24/2010)
Ok I have got myself in a tiz about device CALs now!!How does a web front end not qualify for a device CAL when all external users will be going via this server to access the application?
Furthermore do service accounts that the application uses need CALs?
I ask as we have a small internal application for a limited number of users that will need licensing.
Thanks
Microsoft SQL Server 2008 licensing FAQ
Q. Which licensing model should I choose—the server plus device CAL, the server plus user CAL, or the processor license?
A.
It depends on the specific situation, but here are some general guidelines:
For externally focused server applications. Processor licensing is a better choice for externally focused server applications, such as Internet and extranet scenarios. It is often difficult to count devices or users in these scenarios, so hardware-based pricing is more straightforward.
December 1, 2010 at 8:50 am
Nadrek (12/1/2010)
Kwisatz78 (11/24/2010)
Ok I have got myself in a tiz about device CALs now!!How does a web front end not qualify for a device CAL when all external users will be going via this server to access the application?
Furthermore do service accounts that the application uses need CALs?
I ask as we have a small internal application for a limited number of users that will need licensing.
Thanks
Microsoft SQL Server 2008 licensing FAQ
Q. Which licensing model should I choose—the server plus device CAL, the server plus user CAL, or the processor license?
A.
It depends on the specific situation, but here are some general guidelines:
For externally focused server applications. Processor licensing is a better choice for externally focused server applications, such as Internet and extranet scenarios. It is often difficult to count devices or users in these scenarios, so hardware-based pricing is more straightforward.
Thanks for the official MS word.
However this case is 1 of the few exceptions where CALs may apply. If my extranet is ONLY going to be used by my employees and I know I only have 10 employees then I believe that cals can be used here.
However for anything that is not strongly protected from public use then hardware seems the obvious way to go.
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply