This documentation applies to the 8.1 version of BMC Atrium Core, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

Managing datasets in BMC Atrium Core

Creating datasets in BMC Atrium CMDB to store data provided by different data providers is the first step when importing data.

A dataset is a logical grouping of data. It can represent data from a particular source, a snapshot from a particular date, or other purpose.

Make sure that each data provider has its own import dataset.

You should also note what dataset is your production, or golden, dataset so that you can plan your normalization and reconciliation jobs. By default, the BMC.ASSET dataset is the production dataset. In reconciliation, the production dataset is used in different ways. First, it is used as a master dataset to identify duplicate CIs, matching attributes for the CI in the production dataset with the CIs in the imported datasets. Second, it can be the target dataset in a merge activity so that the CIs are updated to keep the production dataset current and accurate. Also, do not normalize the production dataset because you should normalize CIs before identifying and merging them.

In cases where you need to merge more than one dataset at time, you might want to create an intermediate dataset for merging. For better performance and to minimize impact on users of the production dataset, BMC recommends that you merge one import or discovered dataset at a time with the production dataset. You might want to merge multiple source datasets in separate jobs to an intermediate dataset and then merge the intermediate dataset with the production dataset.

For more information about datasets, see Grouping CIs into datasets.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.