Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

clarify SQL licensing FAQ #464

Closed
aczechowski opened this issue Apr 13, 2018 · 23 comments
Closed

clarify SQL licensing FAQ #464

aczechowski opened this issue Apr 13, 2018 · 23 comments

Comments

@aczechowski
Copy link
Member

@aczechowski aczechowski commented Apr 13, 2018

Frequently asked questions for Configuration Manager branches and licensing
What are the use rights associated with the SQL technology provided with System Center Configuration Manager?

Additional questions to address:

  • Enterprise vs Standard
  • Extra dba stuff like "cmmonitor"
  • PowerBI server for external reporting
  • Database vs instance vs server

Also investigate how to further clarify:

  • 3rd-party (and even 1st-party) add-ons: partner products, MBAM, and MDT

Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

This comment has been minimized.

Copy link

@Silencer0001 Silencer0001 commented Jul 24, 2018 — with docs.microsoft.com

I see this article is updated on 30/04. Does this reflect the full statement of Microsoft after raising your question?
I would like to have an official statement about including the following database to the SQL-Server of ConfigMgr:
- cmmonitor
- ConfigMgr Client Health DB by Anders Rodland
- MDT Database

All the Databases above can be linked to additional functionality for ConfigMgr.
I would generally add features like "PowerBI" and "MBAM" to another (licensed) DB Instance since it's not tightly related to ConfigMgr.

Thanks for the feedback!

@aczechowski

This comment has been minimized.

Copy link
Member Author

@aczechowski aczechowski commented Jul 24, 2018

@Silencer0001, see the following statement in this particular FAQ:

If a database for any additional Microsoft or third-party product shares the SQL Server, you must have a separate license for that SQL Server instance.

At this time, the products that you specify fall into this category.

This comment has been minimized.

Copy link

@Silencer0001 Silencer0001 commented Aug 3, 2018 — with docs.microsoft.com

@aczechowski, thanks for the reply. I thought so, but wasn't sure since this feedback item was still "open". Too bad to hear that it doesn't fall under the standard SQL license. Are there any other native Microsoft solutions available to index and optimise the SQL DB without violating the SQL license terms for ConfigMgr?

This comment has been minimized.

Copy link

@bahtisametcoban bahtisametcoban commented Oct 24, 2018 — with docs.microsoft.com

@aczechowski I have a database to store dba related information such as logins and sizes and so on. Is it also falls into that category?
My second question is what happens if I create sp,table under system databases? I would like to know if that is a problem for licencing.

@aczechowski

This comment has been minimized.

Copy link
Member Author

@aczechowski aczechowski commented Oct 24, 2018

@bahtisametcoban - as you describe might fall into the other category of "extra dba stuff". Still an area we need to clarify, so I don't have a definitive answer. If it's a third-party product, that's definitely something that will require a separate license.
As for adding custom stored procs or tables to the SCCM database...that's not a licensing question but a supportability one.

@aczechowski

This comment has been minimized.

Copy link
Member Author

@aczechowski aczechowski commented Dec 5, 2018

Question from AZSMUG to clarify: customer has Intune through EMS/M365, thus has SCCM. Does that also then include use rights for SQL?

@aczechowski

This comment has been minimized.

Copy link
Member Author

@aczechowski aczechowski commented Dec 6, 2018

  • Is SQL Cluster included? (we only talk about SQL AO)
  • Would a full SQL Standard be also included when used for Secondary sites?
@aczechowski

This comment has been minimized.

Copy link
Member Author

@aczechowski aczechowski commented Dec 11, 2018

See linked #1077, closed as a duplicate of this.

This comment has been minimized.

Copy link

@JBFulc JBFulc commented Dec 14, 2018 — with docs.microsoft.com

@aczechowski just to update since applying the product key for SCCM (that I got from the 365 team) and the server being restarted. SQL has now locked me out as it needs a Licence key too. I have recontacted the same team to obtain a SQL 2017 key which they are looking into. I guess you are looking at the same thing?

This comment has been minimized.

Copy link

@JBFulc JBFulc commented Jan 7, 2019 — with docs.microsoft.com

@aczechowski I am still unable to use SCCM. As SQL is no longer licensed the SQL services cannot be started.
Whom at Microsoft support should I contact to get hold of a SQL licence key?

@JBFulc

This comment has been minimized.

Copy link

@JBFulc JBFulc commented Jan 14, 2019

Question from AZSMUG to clarify: customer has Intune through EMS/M365, thus has SCCM. Does that also then include use rights for SQL?

Is there any clarification on this or do I need to buy a SQL licence separately?
Thanks.

@aczechowski

This comment has been minimized.

Copy link
Member Author

@aczechowski aczechowski commented Jan 15, 2019

I don't have clarity on that yet. I know support is working with the licensing team to help unblock you.

@JBFulc

This comment has been minimized.

Copy link

@JBFulc JBFulc commented Jan 17, 2019

I don't have clarity on that yet. I know support is working with the licensing team to help unblock you.

Is there any timeline on this? Am I able to contact the support team that are looking into this for me?
Thanks.

@JBFulc

This comment has been minimized.

Copy link

@JBFulc JBFulc commented Jan 23, 2019

@aczechowski is there any news from the licensing team?

@russrimm

This comment has been minimized.

Copy link
Contributor

@russrimm russrimm commented Jan 23, 2019

One more clarification that could help - since SQL is licensed by core count, does it matter how many cores the sql standard that's dedicated to sccm has? I'm guessing not, but worth mentioning in the updates.

This comment has been minimized.

Copy link

@faulknerp faulknerp commented Jan 24, 2019 — with docs.microsoft.com

Any update on whether SQL Enterprise licence is covered please? I asked this before but it was closed as a duplicate of #464...

SQL Enterprise is required for AlwaysOn (https://docs.microsoft.com/en-us/sccm/core/servers/deploy/configure/sql-server-alwayson-for-a-highly-available-site-database).
As this page says approved SQL use rights with SCCM include "SQL Server Always On" does that confirm that SQL Enterprise is covered by the license that comes with SCCM?

@JBFulc

This comment has been minimized.

Copy link

@JBFulc JBFulc commented Jan 30, 2019

@aczechowski Is there an appropriate department that my CSP should be talking to? As wording seems to be everything when contacting Microsoft support is there anything specific they should mention?

@aczechowski

This comment has been minimized.

Copy link
Member Author

@aczechowski aczechowski commented Mar 6, 2019

For my own reference:

From licensing terms:

3.2 SQL Server Technology
Customer may run any number of Instances of any SQL Server database software included in the Product in one OSE only for the purpose of supporting that Product and any other Product that includes SQL Server database software.

Direct link to English product terms doc

VLSC lists SQL Standard along with the SCCM current branch download.

With SQL 2016, SQL Reporting Services is a separate download. PowerBI server requires Enterprise edition.

@anwojcie

This comment has been minimized.

Copy link

@anwojcie anwojcie commented Mar 19, 2019

@aczechowski
Statement "Right to run management server software and supporting SQL Server Runtime (SQL Server Standard Edition)"
from https://www.microsoft.com/en-us/licensing/product-licensing/system-center?activetab=product-licensing/system-center-2016-pivot:primaryr2
was sent to my CX recently by LicenseQ

@dsolodow

This comment has been minimized.

Copy link

@dsolodow dsolodow commented Sep 16, 2019

Not sure how it would be worded, but a small user database for management tasks/proc (like OlaHollangren) would seem useful.

This comment has been minimized.

Copy link

@zilvakas zilvakas commented Dec 20, 2019 — with docs.microsoft.com

SCCM is bought through EMS. Questions:

  • How to get SQL license key?
  • is it possible to use any version of SQL (I mean 2014/2016, 2017, 2019)?
@aczechowski

This comment has been minimized.

Copy link
Member Author

@aczechowski aczechowski commented Dec 20, 2019

@zilvakas, see this FAQ. Get a support case open for the ConfigMgr & SQL keys, reference the internal KB article noted in that FAQ.

Regarding version of SQL, see the supported configuration.

@aczechowski

This comment has been minimized.

Copy link
Member Author

@aczechowski aczechowski commented Feb 12, 2020

After much internal discussion, I'm closing this issue. I realize that there are some questions here that are not explicitly answered.

FYI, I did also submit a change to fix related issue #1274.

If you still have further questions, please talk with your Microsoft account manager about your organization's licensing, and review the official product terms.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
9 participants
You can’t perform that action at this time.