Book
Database Design for Mere Mortals, 4th Edition
25th Anniversary Edition
Michael J. Hernandez
Summary
Teaches relational database design as a process to follow step by step, independent of any database product. Hernandez starts with terminology and design objectives, then works through the stages in order: writing a mission statement, interviewing users and management, analyzing the current database, establishing tables, keys and field specifications, defining table relationships, recording business rules, and designing views. Data integrity is reviewed at the field, table and relationship level along the way. Closing chapters show what bad design looks like and when bending the rules is justified. Normalization gets a short section early on and an appendix of its own. Every chapter ends with review questions, answered in an appendix.
Target Readers
- People who have never designed a database and need a method that runs from requirements to tables
- People running an existing database that needs improvement
Tags
Colophon
- Publisher
- Addison-Wesley Professional
- ISBN
- 978-0-13-678804-1
- Published
- Dec 2020
Get this book
* The link above is an advertisement via Amazon Associates.Related Books
Next Books
- Recommended
SQL Queries for Mere Mortals, 4th Edition
A Hands-On Guide to Data Manipulation in SQL
John L. Viescas
Reason: SQL Queries for Mere Mortals begins by checking that the database structure is sound, in its second chapter, before any query is written. Having worked through tables, keys and relationships as a design process first, you can read the join and subquery chapters knowing why the tables connect the way they do. Both books belong to the For Mere Mortals series and neither depends on a particular database product.
- Recommended
SQL Antipatterns, Volume 1
Avoiding the Pitfalls of Database Programming
Bill Karwin
Reason: Database Design for Mere Mortals teaches a sequence for settling keys, field specifications, relationships and business rules, and spends one late chapter on bad design. With that sequence in hand, many of the schema-design antipatterns in SQL Antipatterns can be read as what happens when one of those steps is skipped or misapplied.