From Wikipedia: "A data model is an abstract model that organizes elements of data and standardizes how they relate to one another and to the properties of real-world entities."
If you search the Data Infrastructure Insights documentation for "data model" you won't get much.
 |
| Top 3 results to "data model" search in DII documentation |
But the data model is pretty much what you see in the Data Infrastructure Insights Reporting Schema Diagram.
For example we look at Storage Mapping. Essentially, this is every table with storageId in. And we can search for this super easy in this post An Exploration of the NetApp DII DWH - Columns on Tables in dwh_inventory.
The statement in the above paragraph is not 100% correct. The dwh_inventory schema is not identical to the inventory schema (at least it didn't use to be when you could look in a front-end OCI server MySQL database and compare it to the back-end OCI DWH server MySQL database), but it is close enough. Also, don't forget that there is a massive wealth of data in the the DII Data Lake which isn't in the inventory/dwh_inventory schema, also performance data too.
Storage Mapping: storage.id maps to storageId in ->
- auto_tiering_policy_constraint.storageId
- auto_tiering_policy.storageId
- backend_lun_to_volume.backendStorageId
- backend_lun_to_volume.frontendStorageId
- backend_lun.storageId
- backend_path.storageId
- cluster_switch_port.storageId
- cluster_switch.storageId
- disk_group_to_disk.storageId
- disk_group_to_storage_pool.storageId
- disk_group.storageId
- disk.storageId
- dr_internal_volume_replica.sourceStorageId
- dr_internal_volume_replica.targetStorageId
- dr_qtree_replica.sourceStorageId
- dr_qtree_replica.targetStorageId
- dr_replica.sourceStorageId
- dr_replica.targetStorageId
- dr_volume_replica.sourceStorageId
- dr_volume_replica.targetStorageId
- file_system_to_volume.storageId
- hv_data_store_to_internal_volume.storageId
- hv_data_store_to_volume.storageId
- hv_lun_to_volume.storageId
- hv_nas_share_to_share.storageId
- hv_virtual_disk_to_volume.storageId
- internal_volume.storageId
- iscsi_logical.storageId
- logical.storageId
- nas_cr_logical.storageId
- nas_file_share.storageId
- nas_logical.storageId
- nas_share_initiator.storageId
- nas_share.storageId
- physical_path.storageId
- qtree.storageId
- quota.storageId
- storage_controller.storageId
- storage_node_to_internal_volume.storageId
- storage_node_to_port.storageId
- storage_node_to_storage_pool.storageId
- storage_node_to_volume.storageId
- storage_node.storageId
- storage_pool_to_backend_lun.storageId
- storage_pool_to_disk.storageId
- storage_pool.storageId
- storage_port.storageId
- storage_to_application.storageId
- unknown_logical.storageId
- violation.storageId
- volume_in_storage_pool.storageId
- volume_map.storageId
- volume_mask.storageId
- volume.storageId
Similarly for other mappings we can search in An Exploration of the NetApp DII DWH - Columns on Tables in dwh_inventory for the {object}Id to see which tables it is in.
Comments
Post a Comment