Comparison of features in CMDB 1.0 and 2.0
The following table compares how different features are implemented in CMDB 1.0 and 2.0:
|Feature||CMDB 1.0||CMDB 2.0|
You cannot create a custom report that involves more than two classes (objects).
For example, to generate a report in CMDB that gives data about which LAN endpoints are used by which computers, you must refer to three objects:
Base Element, Computer System, and LANEndPoints.
|All classes are part of one object (as field sets), therefore, you can create reports that involve any number of classes.|
|Field definition of a class||The CMDB_AttributeDefinition class is used to recognize attributes (fields) that belong to a class (object).||The field sets and field definition of the |
|Data import||Records are first imported in a flat table, called staging table, and then saved in the individual objects. Therefore, the batch size is small.||Records are imported directly into the |
|Data export||Exporting data is difficult because one configuration item record is saved in more than one object.||Exporting data is easy because all records are saved in the |
Custom fields are added in the required class.
You can then access them in the class by navigating to the Remedyforce Administration > Configure CMDB 1.0 > CMDB Custom Attributes page.
Custom fields appear on the Custom tab on the Instance Editor.
Custom fields are added to the
|Instance Editor||Custom fields appear on the Custom tab, and you cannot add or remove the fields on the General tab.||To add or remove a field from the General tab, add or remove the field from the Base Element field set. To add or remove a field from the Specifications tab, add or remove the field from the field set of the required class.|
|Field tracking||You can track fields that belong to the ||Because fields of different classes are stored in the |
|Search||You can search fields of the||All fields (or attributes) are stored in the |
Different objects are created for different classes; attributes that are common in all classes are stored in the
When a record is saved, data is saved in the
All information is stored in the
When you save a record, the record is created only in the