- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2024 11:12 AM
We are wanting to weigh the pros and cons of wiping out our current CMDB and starting fresh.
Has anyone gone through this and if so, what does it involve?
Please let me know.
Thanks, Juli
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2024 11:56 AM
Complete wiping of CMDB is typically not recommended except in the case of an initial data population as part of a new ServiceNow implementation (i.e. when CMDB is yet to be operationalized in production and if a lot of corrections are required in the CI data which is loaded). If the CMDB is already in use, then wiping will clear the details of CIs which are referenced in incidents, problems, changes etc. Similarly if hardware assets are managed in ServiceNow, then it will also clear all the asset-CI synchronisation and it might remove a lot of useful attributes populated for the assets.
It is better to undertake a clean up initiative instead by considering the following guidelines:
1. Identify CI classes which were populated whose data is not all required to support any business objectives. For these, you can consider a total cleanup using table cleaner if they were never referenced in any records like incidents, problems, changes etc. in the past (and also if they don't have a sync with an asset record)
2. For records which are identified to be populated in the wrong class, take actions to reclassify them while ensuring to preserve all the required data attributes which are populated. This is explained in the following URL:
3. Ensure that CMDB health metrics are configured for the populated CI classes. Then take actions to correct CI data quality issues. E.g. Processing deduplication tasks to handle duplicate CIs.
4. Refer the insight from 'CMDB and CSDM data foundations dashboard' to further improve CMDB data quality and enhance CSDM alignment.
5. Define archival and retention periods for data in various CI classes. Take actions to archive CIs for which the archival period is crossed since it got 'Retired' (CIs should be always 'Retired' first and not deleted). The archived CIs which have crossed the data retention period can be deleted.
Check my following article for more details about effective CMDB data management:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2024 11:56 AM
Complete wiping of CMDB is typically not recommended except in the case of an initial data population as part of a new ServiceNow implementation (i.e. when CMDB is yet to be operationalized in production and if a lot of corrections are required in the CI data which is loaded). If the CMDB is already in use, then wiping will clear the details of CIs which are referenced in incidents, problems, changes etc. Similarly if hardware assets are managed in ServiceNow, then it will also clear all the asset-CI synchronisation and it might remove a lot of useful attributes populated for the assets.
It is better to undertake a clean up initiative instead by considering the following guidelines:
1. Identify CI classes which were populated whose data is not all required to support any business objectives. For these, you can consider a total cleanup using table cleaner if they were never referenced in any records like incidents, problems, changes etc. in the past (and also if they don't have a sync with an asset record)
2. For records which are identified to be populated in the wrong class, take actions to reclassify them while ensuring to preserve all the required data attributes which are populated. This is explained in the following URL:
3. Ensure that CMDB health metrics are configured for the populated CI classes. Then take actions to correct CI data quality issues. E.g. Processing deduplication tasks to handle duplicate CIs.
4. Refer the insight from 'CMDB and CSDM data foundations dashboard' to further improve CMDB data quality and enhance CSDM alignment.
5. Define archival and retention periods for data in various CI classes. Take actions to archive CIs for which the archival period is crossed since it got 'Retired' (CIs should be always 'Retired' first and not deleted). The archived CIs which have crossed the data retention period can be deleted.
Check my following article for more details about effective CMDB data management:
