Managing data sources and datasets in BMC Helix CMDB
You can also use datasets for partitioning data. For example, you could use datasets to represent production data or obsolete data. Your datasets do not all need to contain different versions of the same CIs and relationships. For example, you could use datasets to hold:
- Subsets of your overall data, such as departments or regions
- Data from different companies for multitenancy
- Test data
A dataset can contain only one instance of a given CI. An instance of that CI might also exist in other datasets to represent the CI in the contexts of those datasets. Instances representing the same CI or relationship across datasets share the same reconciliation identity, or reconciliation ID.
Each CI and relationship in BMC Helix CMDB must reside in a dataset, meaning that they have a DatasetId attribute that must contain a value.
Overview of working with datasets
These are the high-level steps required to create datasets:
- Identify your data sources.
- Create a dataset for each data source that you have identified.
- Import your data source content into the relevant dataset.
The image below gives you an overview of the recommended dataset model
Task or concept | Reference |
|---|---|
Scenarios and the recommended best practices | |
Create a dataset for a data source | |
Modify a dataset | |
Deleting a dataset | |
Know more about the existing datasets that are defined in BMC Helix CMDB upon installation | |
Overlay datasets and how they work | |
Set permissions to various datasets and manage them |