December 14, 2007 at 10:51 am
I have a quick question about SS2005 CAL licensing. In our company we are implementing a piece of middleware that allows communications between our iSeries and external applications. The middleware app uses a SS database only for configuration parameters and such. Our users are only accessing the data on the iSeries.
My question is, do we still need to have a CAL for each user/device accessing the middleware app? I would suspect that we do but the vendor of the app says otherwise and my boss wants to believe them :Whistling:.
December 14, 2007 at 11:10 am
For SQL Server licensing it is licensed by CPU "SOCKET". If you have 2 physical CPU sockets you have to purchase two licenses. They currently do not count the cores, at least not yet. So reguardless of how many connections you make to SQL, you only pay the license per "Socket" not connection. I bet your middleware app licenses by connection.
December 14, 2007 at 11:26 am
If the end-user data being queried by the end-users never "hits" the SQL server, then I would imagine that no, you don't need it. If it's only using it for basic configuration info, I also can't imagine it would need anything other than SQLExpress (which is free and freely licensed).
That being said - it's one of those gray areas, so I'd get a "real" read from the licensing specialist from whatever vendor you get your Microsoft licensing from.
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
December 14, 2007 at 11:35 am
So reguardless of how many connections you make to SQL, you only pay the license per "Socket" not connection. I bet your middleware app licenses by connection.
But we didn't buy processor licenses, only server licenses.
December 14, 2007 at 11:46 am
If the middleware app requires a SQL backend then did you install SQL? If you did install SQL then SQL has to be Licensed.
Or did the middleware app install an instance of the SQL engine? Most likely it is the MSDE version/engine if it did. If its the MSDE then your fine. MSDE is a freebie.
December 14, 2007 at 11:50 am
Keep in mind that by "hit" the server I mean - if the front-end app sends the question to SQL and SQL goes to get the data, returns it and gets rid of it - that's "hitting" the server. If the front-end app gets the question, asks SQL how to "talk" to iSeries and then sends the question to Iseries gets the answer directly from Iseries, then no - that's not hitting the server.
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
December 14, 2007 at 12:02 pm
No, we actually did a separate install of SS2000 Enterprise Edition (load balancing cluster).
@matt-2 - So your saying that even if SS data is used on every call from the end user, if the data is not actually returned to the user, no client license is required?
Forgive my confusion but I have never come across a scenario that only required a server license and no CAL's.
Thank you both for your quick responses.
Brent
December 14, 2007 at 12:08 pm
CAL's are typically licenses required for connecting to a shared resource like a shared directory on your server like "\\yourserver\movies" and "\\yourserver\userdata" or shared printers. When it comes to SQL you are connecting to a SQL service running on the server not a shared anything. So CAL's are thrown out the window when it comes to SQL.
December 14, 2007 at 12:14 pm
I just re-read your original post. If your middleware folks say you do not need to pay for CAL's and you already purchased the SQL license, then you are fine. Since SQL doesn't use CAL's and your middleware peeps say no CAL's either, then pop open a beer and call it a day!
December 14, 2007 at 12:21 pm
My interpretation is that IF the client data transits through SQL Server, then you WOULD have to license CAL's. If the data calls happen from the app directly to iSeries and back (meaning - the actual data the user never goes through SQL Server), and SQL server only has config info and is not involved in the end-user experience in any other way, then I'd think your vendor is correct, and you do NOT need CAL's.
So - even if SQL server might not "hold on" to the data, if it's the one making the request to iSeries, then the end-user is "asking SQL the question", so user-licenses would be required. Otherwise the server license should be enough (in my not authoritative opinion).
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
December 14, 2007 at 12:21 pm
So CAL's are thrown out the window when it comes to SQL.
Whaaaa? Then why does MS mention CAL's in 2 of the 3 primary license models?
1. Processor License
2. Server License with user CAL's
3. Server License with device CAL's
http://www.microsoft.com/sql/howtobuy/licensing.mspx
Can somebody clarify for me??????
December 14, 2007 at 12:23 pm
CAL's are definitely one option for licensing SQL server.
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
December 14, 2007 at 12:26 pm
OK, guys. Sounds like the vendor might not be high, I just wanted to see what you thought. Thanks for all of your input.
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply