MSSQL Instance to Windows Server Relationship

Earlier releases could fail to create the Runs On relationship between MSSQL Instance CIs and their Windows Server CIs during DevOps processing. A JSON parsing exception in the cluster metadata reader caused the relationship transaction to roll back silently, leaving MSSQL infrastructure topology incomplete in the CMDB. The parser now handles this case correctly, and the Runs On relationship is created automatically after each MSSQL discovery and Process DevOps run.

Where the relationship appears

The restored relationship is visible in the following locations:

Location	What changed
CMDB > MSSQL Instance CI > Relationships tab	The Runs On relationship to the host Windows Server CI is created automatically during DevOps processing after MSSQL discovery.
ViVID and Business Service Map	The MSSQL Instance-to-Windows Server dependency is now visible in service and dependency map views.
Dependency and impact analysis	MSSQL infrastructure topology is complete, so service impact analysis correctly accounts for the underlying Windows Server host.

Procedure

Complete the following steps after upgrading to v6.1.2 to create and verify the Runs On relationship for existing MSSQL Instance CIs.

Run Process DevOps after the next MSSQL discovery.

Trigger the Process DevOps job after your next MSSQL discovery run, or wait for the next scheduled run. The corrected cluster metadata parsing logic takes effect automatically and creates the Runs On relationship for each MSSQL Instance CI.
Verify the relationship in the CMDB.

Confirm that the relationship has been created for the affected MSSQL Instance CIs:
1. Go to CMDB and open any MSSQL Instance CI.
2. Open the Relationships tab.
3. Confirm that a Runs On relationship to the host Windows Server CI is listed.
Review the Business Service Map.

Open the Business Service Map for an affected service and confirm that the Windows Server hosting relationship is visible and that the MSSQL infrastructure topology is complete.

Note: The relationship is created during DevOps processing that follows an MSSQL discovery. If the Runs On relationship is still missing after the upgrade, re-run MSSQL discovery and then run Process DevOps again.