Database Design for Mere Mortals: A Hands-On Guide to Relational Database Design (3rd Edition)

Database Design for Mere Mortals: A Hands-On Guide to Relational Database Design (3rd Edition)

Michael J. Hernandez

Language: English

Pages: 672

ISBN: 0321884493

Format: PDF / Kindle (mobi) / ePub


 

The #1 Easy, Commonsense Guide to Database Design! Michael J. Hernandez’s best-selling Database Design for Mere Mortals® has earned worldwide respect as the clearest, simplest way to learn relational database design. Now, he’s made this hands-on, software-independent tutorial even easier, while ensuring that his design methodology is still relevant to the latest databases, applications, and best practices. Step by step, Database Design for Mere Mortals ® , Third Edition, shows you how to design databases that are soundly structured, reliable, and flexible, even in modern web applications. Hernandez guides you through everything from database planning to defining tables, fields, keys, table relationships, business rules, and views. You’ll learn practical ways to improve data integrity, how to avoid common mistakes, and when to break the rules.

 

Coverage includes

Understanding database types, models, and design terminology

Discovering what good database design can do for you—and why bad design can make your life miserable

Setting objectives for your database, and transforming those objectives into real designs

Analyzing a current database so you can identify ways to improve it

Establishing table structures and relationships, assigning primary keys, setting field specifications, and setting up views

Ensuring the appropriate level of data integrity for each application

Identifying and establishing business rules

Whatever relational database systems you use, Hernandez will help you design databases that are robust and trustworthy. Never designed a database before? Settling for inadequate generic designs? Running existing databases that need improvement? Start here.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Figure 10.58 shows the results of your work. Figure 10.58. Designating a Set Default deletion rule for the EMPLOYEES table self-referencing relationship Identifying the Type of Participation for Each Table When you establish a relationship between a pair of tables, each table participates in a particular manner. The type of participation you assign to a given table determines whether a record must exist in that table before you can enter records into the related table. There are two

business rule that pertains to a field can affect one or more elements of that field’s specifications. This is where you indicate the elements the rule affects. • Relationship Characteristics Affected: A business rule that pertains to a relationship will affect one or more of the relationship’s characteristics. Here is where you indicate the characteristics that the rule affects. • Action Taken: Here you indicate the modifications you’ve made to the elements of a field specification or to a

were System R, developed by IBM at its San Jose Research Laboratory in California, and Interactive Graphics Retrieval System (INGRES), developed at the University of California at Berkeley. These two programs contributed greatly to the general appreciation of the relational model. As the benefits of the relational database became more widely known, many companies decided to make a slow move from hierarchical and network database models to the relational database model, thus creating a need for

way of Newton’s theory of gravity. The point is that it works every time. If you chisel a stone flat and place it on another flat stone, you can predict that it will stay where you put it. This theory allows you to design pyramids and cathedrals and brick outhouses. Now consider a database example. Let’s assume you have a pair of tables that are related to each other. You know that you can draw data from both tables simultaneously simply because of the way relational database theory works. The

the interviews you’ll conduct throughout the remainder of the design process. * * * JOHN: “Okay, let’s talk about the Students table. How would you describe a ‘student’?” FRITS: “A student is a private individual who comes in for one of our classes.” SARA: “That’s only partially true. A student can also be an individual that an organization sends to our classes. For example, many of our students come from local banks and insurance companies, and those organizations pay for the students’

Download sample

Download