How SQL Server/windows server licensing is done in Servicenow sam pro?

[MercBuilding]

Hi All,

   I just wanted to understand how sql server licensing will be done. We have created software entitlements for both Standard and Enterprise edition of sql server, we have enough rights as well. But when we run reconciliation it is showing both the products/models as not compliant and nothing is considered as licensed install. What does the system expect to see when we ran recon? Does it make any impact if we have 'is Virtual' flag on cmdb_ci record is set true? if so how this issue can be fixed. ANother question, can we use Server (Per Server) license metric for SQL Server/Windows Server?

Thanks!!

[Joe Ryder]

First, the latter question: Can you use per-server license metric? Yes, if that's how you bought the licenses. However, if you use per-server but actually bought per-core-pair, you won't be able to reconcile correctly at all.

The former question of why the reconcile is not working is a fundamental reason the Microsoft publisher pack must be installed to properly resolve the licensing complexity of WinServ and SQL Server licensing. The relationships with physical servers are unique to the licensing process of MS products. The Microsoft publisher pack adds tables to resolve the logic of licensing per core and covering the VMs related to the physical servers that are actually licensed. It also applies Azure rights and BYOL.

I would recommend using the following to review license position:

https://docs.servicenow.com/bundle/sandiego-it-asset-management/page/product/software-asset-management2/concept/microsoft-publisher-pack.html?cshalt=yes

Dashboard in Classic: https://docs.servicenow.com/bundle/sandiego-it-asset-management/page/product/software-asset-management2/reference/dashboard-microsoft.html

Publisher Overview in Workspace: https://docs.servicenow.com/bundle/sandiego-it-asset-management/page/product/software-asset-management2/reference/publisher-overview-microsoft.html

[Scott Halverso1]

Srinivas Ramanujaiah wrote up a couple blog articles that deep dive into the topic.  We often use the CMDB Query builder to understand the installation estate if MSSQL is deployed in a virtual farm.

Understanding Microsoft SQL Server Licensing in an on-premise Cluster Environment

Optimization vs Allocation on ServiceNow SAM Pro