November 16, 2006 at 3:15 pm
Is a Windows CAL needed for each SQL Server 2005 CAL like Terminal Server?
November 16, 2006 at 3:33 pm
I think that depends on how you do authentication. If you will be using Windows Authentication, then the answer is most likely, yes. If you are using SQL Authentication, then answer is most likely no.
November 16, 2006 at 3:42 pm
The application that access the SQL Server is using SQL authentication.
November 16, 2006 at 3:55 pm
My understanding (which may be flawed) is that if you bought the SQL Server with the 'per cpu' option, then you can hit it with as many folks as it will bear. If you bought it 'per user', then everyone who connects has to have a CAL.
The per cpu on SQL Server 2005 Standard is about $6K per cpu, per user is closer to $2K but its $149 per CAL on top of that. Don't quote me on those numbers, but that's the general idea.
If it connects to the internet, you have to get the per CPU license.
November 17, 2006 at 9:13 am
Yeah I looked at those per server licensing and it would be nice to have if we had the money to spare, we have dual Xeon processors.
Another question on SQL Server CAL's, are they concurrent user? What I mean is if I have 10 CAL's and 15 users but no more then 10 use the front end program at one time. Will I still need only need 10 CAL's or 15?
I'm doing a licensing audit on our servers and after a few days of looking as Microsoft Licensing Agreements and Licensing programs I'm still confused.
November 17, 2006 at 9:28 am
My understanding is that you'd need 15 CALs (one for everyone who could hit the server).
November 17, 2006 at 9:36 am
Thanks, I was affraid of that.
November 19, 2006 at 1:16 pm
Get an ms licensing specialist to look into your requirements. I did. We are licensed per CPU which works out better for us.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply