November 30, 2010 at 8:00 am
Hello, I have to buy sql licenses.
I have a client-server application, the server application is running in the server machine where the sql is installed. The server application connects to sql server with the user "sa".
All the clients (10 is the number of users in my office) use a client application that connect to the server application and don´t know what user is connected to the sql server.
I have 10 license CALS of Windows Server 2003.
I think that I need 1 License for SQL Server and 1 License of user Sql (CAL).
I don´t need 10 license CAL for SQL, because the server application use the "sa" user. Maybe, I don't need a license for user SQL (CAL)
Is that right?
Thanks for your help.
Viky
November 30, 2010 at 8:06 am
Wrong, it's not the amount of logins but the # of peoples.
You need 10 cals. I'd also confirm what is the tipping point between CAL and processor and verify if it's not cheaper to go straight to processor.
At 10 cals licenses it should be cheaper than 1 processor license, but if you think you'll need 20+ in the [not so] near future, you might consider using processor license mode.
November 30, 2010 at 10:11 am
You can use the script on the link below to calculate the break even point for Processor vs. Server/CAL licensing.
Calculate SQL CAL Break Even Point
November 30, 2010 at 10:17 am
Nice script.
I don't want to seem too anal, but I have a Case sensitive server and your script fails @ @edition (lower e).
:hehe:
November 30, 2010 at 10:20 am
Aside: Stop using the sa account. That's so far into the 'worst practices' territory you'll need a map to find it.
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 30, 2010 at 10:25 am
Ninja's_RGR'us (11/30/2010)
Nice script.I don't want to seem too anal, but I have a Case sensitive server and your script fails @ @edition (lower e).
:hehe:
Fixed, I hope.
November 30, 2010 at 10:29 am
Michael Valentine Jones (11/30/2010)
Ninja's_RGR'us (11/30/2010)
Nice script.I don't want to seem too anal, but I have a Case sensitive server and your script fails @ @edition (lower e).
:hehe:
Fixed, I hope.
Yes it works now. Tx :w00t:
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply