User Tools

Site Tools


replicator_servicenow_hierarchy

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
replicator_servicenow_hierarchy [2017/05/12 10:33]
jackson performance changes with 3.21.0
replicator_servicenow_hierarchy [2018/04/10 12:16] (current)
paul.jensen changed than to then
Line 13: Line 13:
 </​WRAP>​ </​WRAP>​
  
-If we have a Linux Server (cmdb_ci_linux_server) traced in red, than that record will exist in the leaf, or child most class, as well as at every single parent level. ​ So that same record can be found in cmdb, cmdb_ci, cmdb_ci_hardware,​ ..., containing the data that pertains to that level.  ​+If we have a Linux Server (cmdb_ci_linux_server) traced in red, then that record will exist in the leaf, or child most class, as well as at every single parent level. ​ So that same record can be found in cmdb, cmdb_ci, cmdb_ci_hardware,​ ..., containing the data that pertains to that level.  ​
  
 In other words the record for Linux Server will have all the data that the parent tables would have and more.  The parent tables would have a subset of data the child table would have.  Every Server is a Computer, but not every Computer is a Server.  ​ In other words the record for Linux Server will have all the data that the parent tables would have and more.  The parent tables would have a subset of data the child table would have.  Every Server is a Computer, but not every Computer is a Server.  ​
replicator_servicenow_hierarchy.txt ยท Last modified: 2018/04/10 12:16 by paul.jensen