RelationalDBDesign 




Database Analysis   «Prev 

Relational Notation explained for Relational Database Management Systems

CD Entity to be transformed into table
CD Entity to be transformed into table

  1. CD: This is the entity
  2. Items in the parentheses: These are the attributes of the CD entity
For the scaling of values the distances should be relevant and not absolute.
One of the reasons you use data mining is to figure out targeting.


Relational Notation

Relational notation is a process of transforming an Entity Relationship Diagram into a more friendly and usable type of diagram that is easily readable. This can be done by taking the names of each table and its attributes and ordering them in a specific order. You always start with the primary key(s), which are commonly notated with the underscore, then all other attributes are added. The only rule for attributes is if it happens to be a foreign key it needs to be underscored with a dotted line.

The final step of database modeling evolution is applications and how they affect a database model design. An application is a computer program with a user-friendly interface. End-users use interfaces (or screens) to access data in a database. Different types of applications use a database in different ways and this can affect how a database model should be designed. Before you set off to figure out a design strategy, you must have a general idea of the kind of applications your database will serve. Different types of database models underpin different types of applications and you must understand where different types of database models apply.
It is essential to understand that a well-organized design process is critical to success. In addition, a goal to drive the design process is equally as important as the design itself. There is no sense designing or even building something unless the target goal is established first, and kept foremost in mind.