For many new or intermediate database developers, it’s difficult to know where to start when designing a relational database. It’s easy to make the mistake of assuming that the functionality of a database will take shape over time, or the design will fall into place as you build the database.

This course introduces a process for effectively planning and designing a functional, efficient database. Knowing how to plan a relational database is important to the success of the databases you create. Without planning, you cannot possibly know what the database needs to do, or even what information to include in the database. Planning a database is essential and prevents the extra work of fixing data maintenance problems later on.

The concepts are not specific to a particular software application and can be applied to any relational database management system.

Course Objectives

In this course, you will perform steps to design a relational database, including gathering requirements, data modeling, and planning implementation.

You will:

  • Follow an efficient process for designing a relational database.
  • Define the database conceptual model.
  • Define the database logical model.
  • Apply database normalization methods to improve the initial design of a database.
  • Complete the database design, including controls to ensure its referential integrity and data integrity.

Target Student

This course is designed for students who need to learn database design essentials, typically in preparation for, or as a supplement to, a course on SQL such as Logical Operations' SQL Querying: Fundamentals (Second Edition) and courses on specific relational database platforms.


To ensure your success in this course, you should have fundamental computer skills. You can obtain this level of skills and knowledge by taking the following Logical Operations course:

  • Using Microsoft® Windows® 10

Course Content

  1. 1
    • Identify Database Components

    • Identify Common Database Design Problems

    • Follow a Database Design Process

    • Gather Requirements

  2. 2
    • Create the Conceptual Model

    • Identify Entity Relationships

  3. 3
    • Identify Columns

    • Identify Primary Keys

    • Identity and Diagram Relationships

  4. 4
    • Avoid Common Database Design Errors

    • Comply with Higher Normal Forms

  5. 5
    • Adapt the Physical Model for Different Systems

    • Ensure Referential Integrity

    • Ensure Data Integrity at the Column Level

    • Ensure Data Integrity at the Table Level

    • Design for the Cloud

For More Information, Call (714) 505-3475

or email us at