1. Appropriate tables

« Previous Chapter

Next Chapter »

When designing a good database, you should not have too many or too few tables, but have the appropriate tables necessary for your applications. There is no hard and fast rule on the number of tables that should be used when designing a database because it solely depends on your application.

Inexperienced database designers use too few tables by cramming up an entire database’s information into a single table, and some database designers use too many tables and each may contains only a few fields. So avoid this and choose an optimum number of tables depending on your application.

« Previous Chapter

Next Chapter »

Table of Contents

» Chapter 1 - Appropriate tables
Chapter 2 - Appropriate Naming Conventions
Chapter 3 - Avoid Data Repetition
Chapter 4 - Avoid Data Redundancy
Chapter 5 - Avoid Null Values
Chapter 6 - Use Constraints
Chapter 7 - Use Triggers
Chapter 8 - Use Stored Procedures

[top]