June 15, 2016 at 7:24 am
Is there a difference in licensing for SQL Server for installing the SQL Native Client on a server verses installing SQL Server?
This is all from an Enterprise install package and they are installed on different servers. We have an app server with just the native client, our database server with the full monty (so to speak) and a web server with just SSRS Native on it. As we're redoing our new environment a bit, I'm counting out our licenses to verify my count vs what corporate has us down for (I don't have details on what our corporate office negotiated license-wise with MS, but I'm assuming a Core vs Server+CAL since we've never given corporate user counts). And I'm wondering if I count them all with the same weight for licensing purposes.
I did download the Licensing Guide from Microsoft and see that the SSRS Native would count as one and the DB server would count as a another. It's the SQL Native Client by itself that I have the question on.
Can SQL Native Client be installed for free (sort of like SQLExpress) or does that count as a full license?
June 15, 2016 at 7:29 am
my understanding is that anything that comes under client tools or connectivity does not need to be licensed
---------------------------------------------------------------------
June 15, 2016 at 8:10 am
my understanding is similar to George's:
services consume licenses, but tools and connectivity do not. that's reinforced by the same tools being part of a separate downloadable install package.
only when you spread services across more than one server, would you need to obtain additional licenses.
Lowell
June 15, 2016 at 8:15 am
What about multiple instances on one server? If it's per core, do you multiple the cores times the number of instances? Or just count the cores once?
June 15, 2016 at 8:20 am
you license a server, so the number of instances do not affect it.
---------------------------------------------------------------------
June 15, 2016 at 8:21 am
Lowell (6/15/2016)
my understanding is similar to George's:services consume licenses, but tools and connectivity do not. that's reinforced by the same tools being part of a separate downloadable install package.
only when you spread services across more than one server, would you need to obtain additional licenses.
I know I've read that multiple sql instances on the same server are covered under the normal license, as long as we are not talking about a bunch of Virtual machines.
Lowell
June 15, 2016 at 8:24 am
Lowell (6/15/2016)
Lowell (6/15/2016)
my understanding is similar to George's:services consume licenses, but tools and connectivity do not. that's reinforced by the same tools being part of a separate downloadable install package.
only when you spread services across more than one server, would you need to obtain additional licenses.
I know I've read that multiple sql instances on the same server are covered under the normal license, as long as we are not talking about a bunch of Virtual machines.
I'm talking the same server name (whether virtual or physical). Not individual virtual servers on the same box.
June 15, 2016 at 8:25 am
Thanks you guys. This helps.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply