Database Design

I used this as one of 2 textbooks to teach an Advanced SQL Database class and though it was very thorough and well laid out

I bought this book to learn some more formal concepts of database design; for work. It is an excellent book, definitely buy this.

I don't think I ever could have read this book when I was just beginning with database design. This is not because it's overly complex, but because the writing is excruciatingly dry and methodical. Having said that, and having had a few years of database programming, I now wish I had read this much sooner. Like many other self-taught programmers, I eventually realized that discipline, patience, and attention to a methodical process actually save time and are far more valuable traits for a database programmer than sheer intuition. For example, if you weren't thorough in gathering requirements, you're going to have to make up for this by repeating interviews during logical modeling. If you weren't thorough in physical modeling, well, re-engineering an existing database full of data is no small task. A lot of the writing here is purely definitional (business rules, ERDs and process models, join types), and the concepts probably won't sink in until you sink your teeth in and actually do the work. However, the value of this book for someone with some working knowledge of database design is that it 1) provides you with a standard language that will help you communicate with other programmers, 2) will help fill in gaps in your knowledge, and 3) provides you with a series of checklists for each stage of the process (such as interviewing customers) to help ensure that you design databases more methodically and don't leave out any key steps. These concepts are so universally applicable in database programming that it really doesn't matter that this book is several years old. It's still relevant.

Recently, I worked with a few developers who were tasked with developing their own database, and soon realized that many developers are not disciplined database designers (myself included). Instead of struggling through ambiguous database designs and creating more work in the coding of business objects, I picked up a book. Database Design, by Ryan K. Stephens and Ronald R. Plew, provided a great foundation for me, and would probably be a good reference for many levels of developers, business analysts, and DBAs. The book starts with an overview of the database design process. At times this section seemed basic for someone that has been through countless development cycles, but the section reiterates concepts that many may take for granted. For instance, the database design process of requirements gathering, logical modeling, and normalization is discussed. Also, from an academic perspective some history and non-traditional methods are reviewed that provide interesting contrasts to how the process of database design has evolved over time. The second section begins to get into the technical meat. The second section discusses gathering business and system requirements. This also provides many good examples of how to translate the business model into database entities. The different forms of normalization are discussed with examples from the first, second, third, Boyce-Codd, fourth, and fifth normal forms. The authors also take the readers through the process of developing Entity Relationship Diagrams (ERDs) and uses accompanying examples. The third section takes the concepts that are used from part two to design tables within the database. Consideration of storage, referential integrity, ownership, performance is all discussed as part of the physical design process. The authors also discuss enforcing business rules and view designs as well. The final chapter of this section ends in a real world scenario of a grocery store owner that wants to model his business activities into a live database. The book provides step by step re-iteration of the process involved in collecting business requirements, modeling data, normalization, and design. The author walks the reader through the process and shows how a designer would create a database from the information provided by the business owner. I thought this was a great example of how the books brought together concepts into real world situations. Kudos for the authors including some non-academic material. Last, the authors discuss other areas that affect the database after the initial design. These areas include security, change control, analyzing legacy data. Each area includes examples and scenarios a DBA might encounter. Overall, I thought this book laid down the foundations for database design very well. I think the authors had some very specific real world experiences that seemed useful during the discussions of the design process. The only con of this book was brief discussions about toolsets bein

After thumbing through a half-dozen books on data modelling and database design, I finally picked up this book. It is the best intro to data modelling that I've come across yet. I've been playing with Oracle and MySQL for a year or so, but I knew I wasn't going to get very far if I didn't know how to build databases from scratch. This book was the first one I've come across that didn't take on the airs of an academic dissertation. Highly recommended for people who want to build Database Analyst skills.