CMDB Multisource table has large number of records, may I know the impact of cleanup this table?

[Vini]

Hi Team,

CMDB Multisource table has large number of records and it occupied 1 TB of storage.

1.   I’d like a summary of it’s purpose and why would or should use this?  Or, is it possible/suggested to disable and not use it and what are the ramifications of doing so?  If so, what are the steps to successful shutdown?
2. If not shutdown can we enable table cleaner on this table and we are trying to understand the impact.

Please advise.

Regards,

Vinil.

[Danie Biesiada1]

This table is crucial for CMDB 360 view, if you have multi source CMDB (ServiceNow Discovery, SCCM and others)
this might be crucial to see what values came for particular CI from different data sources.   

What I would suggest is removal of data after CI is end of life plus some number of days. 
You can create a scheduled job for that. 

[Sandeep90]

@Vini There are cleanup job 'CMDB Mulitsource Cleanup' that cleans invalid records periodically and uses the below settings to change or disable Mulitsource if you are not using it.  One I would suggest is if you are not using CMDB 360 for non cmdb data disable this property 'glide.identification_engine.multisource_non_cmdb_ci_enabled' 

https://docs.servicenow.com/bundle/vancouver-servicenow-platform/page/product/configuration-manageme... 

[Vini]

Thank you for your response @Sandeep90 , We would like to disable Multi source permanently in all tabled in CMDB.

[Sandeep90]

just set the 'glide.identification_engine.multisource_enabled' to false.