- database designers,
- application architects,
- database administrators, and
- project managers
should ideally understand what makes a good database design. Even an application's key customers and users could benefit from understanding how databases work.
Many IT professionals have learned what they know about databases through rumor, trial-and-error, and painful experience.
Over the years, some develop an intuitive feel for what makes a good database design but they may still not understand the reasons why a design is good or bad, and they may leave behind a trail of rickety,
poorly constructed programs built on shaky database foundations.
This book provides the tools you need to design a database. It explains how to determine what should go in a database and how a database should be organized to ensure data integrity and a reasonable level of performance.
It explains techniques for designing a database that is strong enough to store data safely and consistently, flexible enough to allow the application to retrieve the data it needs quickly and
reliably, and adaptable enough to accommodate a realistic amount of change.