Basics of Database Design

by Jamal A
The article I read talks about the basics of database design including normalization, relationships and cardinality. It is important to create an entity relationship diagram (ERD), but sometimes it is ignored or overlooked when developing an application. Developers can use an accurate data model as an important reference tool. Effective database design can help developers to develop applications that perform well from the beginning. The effective database design can help developers to reduce the overall time it takes to complete the project. According to the article, effective database designers should use the principles of normalization when designing a database. Normalization is a database design approach that includes four objectives, minimization of data redundancy, minimization of data restructuring, minimization of I/O by reduction of transition sizes, and enforcement of referential integrity. The concepts and techniques that is important when designing an effective database will be discussed later on in this summary. The article describes the physical corresponding item of an entity is a database table. Naming entities should be in singular form and in all caps. For example, “an entity that contains data about your company’s employees would be named EMPLOYEE”.  The second corresponding item of an attribute is a database column. In database column one must name their database attributes in singular form with either capital letters or in all lower case. “For example, some attribute names for your EMPLOYEE entity might be: EmployeeId (or employee_id) and BirthDate (or birthdate)”. The third corresponding item that is described in this article is a primary key. The primary keys uniquely identify a row in a table and relate records to additional data stored in other tables. The primary Key simply points between interrelated records in different tables. Next, different types of relationships are described in this article for example, “one-to-many, and “many-to-many relationships. These are some of the basics that are described in this article.

This article is related to the class because it talks about the importance of creating an entity relationship diagram. It also describes how effective database design can help developers to reduce the overall time it takes to complete the project. I remember, I was having some difficulties retrieving data from SQL server, because my entity relationship diagram was not accurate. I learned a lot from this article, I believe simple detail can make a big difference when creating an entity relationship diagram.


Huscher, B. (2000, June 30). Database Design and Modeling Fundamentals – SQL Server Information at Retrieved February 19, 2012, from

1 thought on “Basics of Database Design”

  1. My article was on database vendors and I think that has a big impact on database design. New systems may not always be safer or more efficient with the downside of being more costly. I suppose companies just have to weigh the costs vs. benefits when designing a database.

Comments are closed.