Video : ER/Studio Enterprise Team Edition
Document Databases. Part 3: As Part of Broader Data Modeling Initiatives
The documentation of a database with an enterprise logical data model mapped to multiple separate physical data models can be a complex task. But it is essential to ensure that one manages and organizes all data. Here are the steps to follow:
- Create an enterprise logical data model: Start by creating an enterprise logical data model that represents the high-level entities and relationships common to all physical data models. This model should be independent of the specific physical data models used.
- Map the logical data model to the physical data models: Once one creates the enterprise logical data model, map it to the multiple separate physical data models. Do that by identifying which entities and relationships are present in each physical data model. This will help to ensure consistency and accuracy across all physical data models.
- Document the enterprise logical data model: Document the enterprise logical data model by including all entities, attributes, and relationships, as well as any other relevant information about the data model.
- Document each physical data model: Document each physical data model, including all entities, attributes, relationships, and any other relevant information specific to that model. Be sure to include the mapping between the logical data model and the physical data model.
- Identify dependencies and relationships between physical data models: Identify the dependencies and relationships between the physical data models, and document them. This will help to ensure that changes in one physical data model do not affect the others.
- Document any data transformation processes: If there are any data transformation processes between the physical data models, document them to ensure that one implemented them correctly.
- Validate the documentation: Validate the documentation to ensure that it represents the enterprise logical data model and all the physical data models.This will help to ensure that all physical data models are consistent and accurate.
Watch this video to discover how to document a database using ER/Studio as part of a broader data modeling initiative, with an enterprise logical model mapped to multiple separate physical data models.
Learn how to reverse engineer a database then document the physical model with business friendly metadata using IDERA’s ER/Studio in this video series:
Part 1: Documenting a Database with ER/Studio – Overview
Part 2: Document a Database As Part of a Localized Initiative with ER/Studio
Part 3: Document a Database As Part of a Broader Data Modeling Initiative with ER/Studio
Part 4: Document a Database As Part of a Data Governance Initiative with ER/Studio
- Webcast: 10 ER/Studio Productivity Tips to Help You Love Your Data Models
- Webcast: Making Connections: Enhance Data Models with ER/Studio 2016+
- Video: Agile Change Management in ER/Studio Data Architect Professional
- Video: Build a Logical Data Model with ER/Studio Data Architect
- Video: Data Modeling for Hadoop Hive with ER/Studio Data Architect
- Video: Data Modeling for MongoDB with ER/Studio Data Architect
- Video: Data Modeling Techniques for Teradata Users
- Video: Why Should A Data Modeler Care About Business Processes?
- Datasheet: Model Hadoop Hive for the Hortonworks Data Platform (HDP)
- Solution Brief: MongoDB Data Modeling with ER/Studio
- Solution Brief: Enterprise Data Modeling: 7 Mistakes You Can’t Afford to Make
- Solution Brief: Importing ER/Studio Data Models into WhereScape 3D
- Case Study: Global Financial Services Organization Turns to ER/Studio for High-Performance Data Modeling
- Case Study: Microsoft Deploys ER/Studio to Establish an Enterprise Data Model
- Case Study: Newmont Mining Standardized their Data Modeling Practices with ER/Studio
Topics : Data Governance,Data Modeling,Enterprise Architecture,
Products : ER/Studio Data Architect,ER/Studio Enterprise Team Edition,