How do you manage "non-specific" versions of SQL Server licenses?

[ClayB]

Our Microsoft License Statement had many instances of non-specific versions of SQL Server imported into ServiceNow. The problem we are facing is that the "any Version and/or Edition" SQL Server software model is showing 111 unlicensed installs. Adding the "Discovery Model > Version" column (see below) shows that there is an associated version (in most cases). 

How can we get these unlicensed installs into their appropriate software model and out of the any Version an/or Edition"? This is currently showing as the only non-compliant software model under SQL Server.

[Ryan97]

A few questions:
1.) Do you have entitlements setup to match these?
2.) Are these virtual installs?
3.) If virtual, do the VMs have their physical hosts & cluster relationships in SN?

[ClayB]

Hi Ryan, please see my answers below. Thanks for your response.

1.) Yes, we currently have entitlements imported for this any version SQL Server software model, as well as the versions listed in the unlicensed installs.

2.) It looks like 90% of these are VMware, so yes. There are several entries that show as "Unknown".

3.) Not that I'm aware. Could you advise on how this can be checked?

[Ryan97]

If they are virtual servers, with no physical host, they will NOT reconcile.  They will just sit in an "unlicensed" state, with no remediation options.  If you want to see if you have a physical host, you can see CI record by looking at the relationships, or you can go to the cmdb_rel_ci table, and search in the Parent/Child columns for your machine.  If there is no parent/child, you have incomplete discovery of your virtual infrastructure, and you will not get a license position.

As another poster said, the Health Checker can also give you some things to look at.  Looking at your screenshots, many of your records seem to have proper editions/versions, but there are a few records lacking editions which will not reconcile until your discovery data is complete for those. 

[dreinhardt]

Hello @ClayB ,

with reference to my projects, the first focus should be the correct detection of the edition. Based on the details you've shared, I would recommend to normalize all SQL Server discovery models to the most detailed level you can get out of the raw inventory data (editon & version would be perfect). This is manual task.

• Manually normalize a software discovery model (servicenow.com)
• Normalization suggestions for discovery models (servicenow.com)

Second, for all discovery models without edition/version details provided by the inventory system, you've to troubleshoot the discovery logs. Please ensure you've installed the latest discovery pattern packages mentioned in the docs. The discovery process for SQL Server triggers several pattern/probes to detect the edition.

• Microsoft SQL Server and Cluster discovery (servicenow.com)
• Optimizing Microsoft SQL Server database and component license consumption (servicenow.com)

Third recommendation (Thanks to @Ryan97), please install the ITAM Health Check App from the ServiceNow Store, this app includes a lot of checks to ensure the ITAM SAMP data is trustworthy. Please focus in SQL Server and Windows Server findings.

• ITAM Health Check release notes (servicenow.com)

Last recommendation, upgrade to the Washington release to get more insights into the reason why a software install record is marked as not licensed and need special actions.

Best, Dennis