What is the backend table name of Data Refresh Rules ?

girijasankar
Tera Contributor

yesterday

Anyone knows, backend table name of Data Refresh Rules which is maintained inside Recon rules. I have found a table name "cmdb_health_staleness_rule" but its related to Health, not related to Data refresh rule. If anyone can provide me please that would be helpful.

The goal is to find how many data refresh rule exists in our instance.

0 Helpfuls
  • 216 Views
2 REPLIES 2

tiagomacul
Giga Sage

yesterday - last edited yesterday

Hi! It is a common point of confusion since ServiceNow has different ways to measure 'data age.'

 

You are correct that cmdb_health_staleness_rule is for CMDB Health, which only flags CIs as stale. However, Data Refresh Rules are part of the IRE (Identification and Reconciliation Engine) logic and are used to determine if a specific data source is still authorized to update a CI based on the last time it provided data.

The backend table name you are looking for is: cmdb_datasource_last_update

https://<instance>.service-now.com/now/nav/ui/classic/params/target/cmdb_health_staleness_rule_list.do%3Fsysparm_clear_stack%3Dtrue

 

 

A few tips for your audit:

  1. Data (Timestamps): The table cmdb_datasource_last_update stores the actual timestamps of when a source last touched a CI. The IRE engine compares these timestamps against the definitions in your reconciliation rules to decide if the data is still valid.

    https://<instance>.service-now.com/now/nav/ui/classic/params/target/cmdb_datasource_last_update_list.do%3Fsysparm_clear_stack%3Dtrue

     

  2. Relationship: Remember that these rules are linked to your Reconciliation Rules (cmdb_reconciliation_definition). A Data Refresh Rule doesn't act alone; it defines the 'shelf life' of data from a specific source before the IRE considers that source no longer reliable for that attribute.

    https://<instance>.service-now.com/now/nav/ui/classic/params/target/cmdb_reconciliation_definition_list.do%3Fsysparm_clear_stack%3Dtrue



  3. Strategic Insight: From an Enterprise Architecture and Now Create perspective, having too many Data Refresh Rules can sometimes indicate a struggle with Data Governance (Pillar 5 of Digital Transformation).

     

     

  4. Cleanup (Purging): If your goal was to physically delete old records from the database based on age, you would use the Table Cleaner (sys_auto_flush), where retention is defined in seconds.
https://<instance>.service-now.com/now/nav/ui/classic/params/target/sys_auto_flush_list.do%3Fsysparm_clear_stack%3Dtrue

 

 

Ideally, you want a lean set of rules that prioritize your most trusted discovery sources (like ServiceNow Discovery or Service Graph Connectors) to ensure your CMDB remains a 'Single Source of Truth'.

 

 

If you're exploring how to better govern your CMDB and IRE via official methodologies, feel free to check out the Now Create assets on the Success Portal or this practical guide: ServiceNow Now Create: Practical Methodology

0 Helpfuls

VijayaMannapura
Tera Guru

yesterday

@girijasankar  The backend table name for these rules is : cmdb_datasource_staleness 

0 Helpfuls