Query about CI relationships of deleted CIs, CMDB CI licensing

Supratik1
Giga Contributor

Hi All,

 

We are performing a cleanup activity of CMDB , by deleting specific CI data from tables due to licensing constraints. 

The records which we are wanting to delete, also contain certain upstream and downstream relationships to other CIs. For example, in the screenshot below, the Virtual Machine Instance CI record I want to delete, has upstream relationship with another ESX server, and downstream relationships with vCenter folder and vCenter datastore CIs.

 

 find_real_file.png

 

My query is the following: If I delete the above CI record, will it lead to creation of any orphan records in CMDB, which in turn may affect the ITSM processes?

Additionally, is there any other way to restrict licensing of CIs by deactivating/disabling them in any way? Please suggest with your valuable inputs.

 

Thanks a lot in advance!

1 ACCEPTED SOLUTION

Rahul Priyadars
Tera Sage

In Terms of ITSM and CMDB there is nothing called Licensing based on CIs.

Licensing comes into Picture when you use ITOM like Discovery and Event Management licenses/Subscription are based on Host/Node.

Point here is Host/Node is not active on Network then obviously it will not be discovered and no event will come So when u disable the CI record it will work and License will be excluded.

find_real_file.png

Hope this helps.

Regards

RP

View solution in original post

8 REPLIES 8

doug_schulze
ServiceNow Employee
ServiceNow Employee

Cascade delete only takes place for referenced records, not the relationships you are speaking of. In your scenario licensing would only impact the virtual instance that you want to delete but the relationships would be remnants that would be orphaned because there's no OOB 'cascade' delete mechanism for them yet. However...

You might be able to incorporate the work that's been done here around retiring CIs. The big script at the end will look through and delete the relationships and other referenced records. Do know, me and my friend @emir.e.eminovic are actually redesigning the process, so if you have some patience it will be even better.

@emir.e.eminovic  The Fix script link in the Get Well Playbook is broken.  

Nikh1
Giga Contributor

@doug.schulze The link is broken. Do you have any update on this. Thanks ..

doug_schulze
ServiceNow Employee
ServiceNow Employee

Apologies, try this ....