A properly designed database provides you with access to up-to-date, accurate information.
Because a correct design is essential to achieving your goals in working with a database, you are much more likely to end up with a database that meets your needs and can easily accommodate change.
The database design process consists of the following steps:
Determine the purpose of your database.
Find and organize the information required.
Divide the information into tables.
Turn information items into columns.
Specify primary keys.
Set up the table relationships.
Refine your design.
Apply the normalization rules.
Certain principles guide the database design process.
The first principle is that duplicate data is bad, because it wastes space and increases the likelihood of errors and inconsistencies.
The second principle is that the correctness and completeness of information is important.
If your database contains incorrect data, any reports that pull data from the database will also contain incorrect data.
As a result, any decisions you make that are based on those reports will then be misinformed.
Relational database design uses either one of the two methods:
Normalization, a series of steps followed to obtain a database design that allows for efficient access and storage of data in a relational database.
ER (entity-relationship) modeling, dividing your database in two logical parts, entities (such as “customer” and “product”) and relations (such as “buys” and “pays for”).
My wife and I have reached the difficult decision that
we do not want children. If anybody does,
please just send me your contact details and
we can drop them off tomorrow.