Relational (OLTP) Data Modeling

Download as pdf or txt
Download as pdf or txt
You are on page 1of 2

Relational(OLTP) Data Modeling

Relational Data Model is a data model that views the real world as entities and relationships.
Entities are concepts, real or abstract about which information is collected. Entities are
associated with each other by relationship and attributes are properties of entities. Business
rules would determine the relationship between each of entities in a data model.

The goal of relational data model is to normalize (avoid redundancy)data and to present it in a
good normal form. While working with relational data modeling, a data modeler has to
understand 1st normal form through 5th normal form to design a good data model.

Following are some of the questions that arise during the development of entity relationship
data model. A complete business and data analysis would lead to design a good data model.

1» What will be the future scope of the data model? How to normalize the data?
2» How to group attributes in entities?
3» How to name entities, attributes, keys groups, relationships?
4» How to connect one entity to other? What sort of relationship is that?
5» How to validate the data?
6» How to normalize the data?
7» How to present reports?

Steps to create and maintain a new data model from business requirements:

These are the general guidelines to create a standard data model and in real time, a data
model may not be created in the same sequential manner as shown below. Based on the
enterprise's requirements, some of the steps may be excluded or included in addition to these.

Sometimes, data modeler may be asked to develop a data model based on the existing
database. In that situation, the data modeler has to reverse engineer the database and create a
data model.

Steps to create a Logical Data Model:

1» Get Business requirements.


2» Analyze Business requirements.
3» Create High Level Conceptual Data Model. Get it approved.
4» Create a new Logical Data Model. Add the following to the logical data model.
5» Select target database where data modeling tool creates the scripts for physical schema.
6» Create standard abbreviation document for naming logical and physical objects according
to business/data modeling standard.
7» Create domain.
8» Create rule.
9» Create default.
10» Create Entity and add definitions.
11» Create attribute and add definitions.
12» Assign datatype to attribute. If a domain is already present then the domain should be
attached to attribute.
13» Add check constraint/rule or default to the columns (wherever it is required).
14» Create primary or unique keys to attribute.
15» Create unique index or bitmap index to attribute.
16» Based on the analysis, create surrogate key columns.
17» If required, create super types and sub types.
18» Analyze the relationship between entities and Create foreign key relationship (one to
many or many to many) between those entities.
19» Create subject areas and add relevant entities to those subject areas.
20» Align the objects in the main subject area and other subject areas.
21» Validate the data model.
22» Generate reports from the data model.
23» Take a print out of the data model.
24» Get it approved.

Steps to create a Physical Data Model:

1» Create Physical Data Model from the existing logical data model.
2» Add database properties to physical data model.
3» Generate SQL Scripts from Physical Data Model. Tick or check the necessary parameters
in the tool, create scripts and then forward that to DBA. (DBA will execute those scripts in
database).
4» Compare database and data model. Make sure everything is okay.
5» Create a change log document for differences between the current version and previous
version of the data model.

Maintenance of Data Models::

1» Maintain Logical & Physical Data Model.


2» For each release (version of the data model), try to compare the present version with the
previous version of the data model. Similarly, try to compare the data model with the
database to find out the differences.

You might also like