yanci1179
asked on
SQL Server 2012 Standard Edition Licensing Cost
We are upgrading to SQL Server Standard Edition 2012. Our legacy applications use distributed queries. We called our DBA and asked if we could have this turned on. Our DBA informed us that if distributed queries is turned on then the model goes from CAL license to CORE license. Since we have 16 cores, this is too much for us. I have tried looking this up in Microsoft license cost website, but can't find anything that says this. Anyone run into this? Did your cost go up as well once you turned on distributed queries?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Vitor Montalvão
I don't think so. MSDTC is the component that you need for Distributed Transactions and is to allow the SQL Server instances installed in the server to connect other databases, not only SQL Server databases as it can be Oracle ,Sybase, DB2, Informix, you name it.
ASKER
Hi Kanti,
Am I understanding this correctly?
I see from your article that license model might change to core the more users you have.
If distributed queries is opened, then we are not able to account for the number of users that have access to the database. So if the number of users is undetermined, it’s recommend to just go with CORE model. Is that accurate?
Am I understanding this correctly?
I see from your article that license model might change to core the more users you have.
If distributed queries is opened, then we are not able to account for the number of users that have access to the database. So if the number of users is undetermined, it’s recommend to just go with CORE model. Is that accurate?
What is your understanding of "distributed queries"?
As I said above, that means your SQL Server instance is allowed to run queries on other databases, so it's a connection from your SQL Server instance to other databases and not the opposite, so you should not count them as connections to your instance.
Here's the MSDN article about distributed queries.
As I said above, that means your SQL Server instance is allowed to run queries on other databases, so it's a connection from your SQL Server instance to other databases and not the opposite, so you should not count them as connections to your instance.
Here's the MSDN article about distributed queries.
ASKER
I am aware that distributed queries are used to connect to other databases in different servers.
In my case, opening distributed queries on both servers, will cause more connections on the second server. This is why the DBA is requiring us to go to the core model
In my case, opening distributed queries on both servers, will cause more connections on the second server. This is why the DBA is requiring us to go to the core model
Hi
Yes if you cannot determine the approx size of users then the CORE route would be suggested.
Yes if you cannot determine the approx size of users then the CORE route would be suggested.