PDF Ebook Database Design and Relational Theory: Normal Forms and All That Jazz (Theory in Practice), by C. J. Date
Database Design And Relational Theory: Normal Forms And All That Jazz (Theory In Practice), By C. J. Date. Negotiating with reading practice is no need. Reviewing Database Design And Relational Theory: Normal Forms And All That Jazz (Theory In Practice), By C. J. Date is not kind of something marketed that you can take or not. It is a point that will alter your life to life a lot better. It is the thing that will provide you several points worldwide as well as this cosmos, in the real world as well as right here after. As what will certainly be provided by this Database Design And Relational Theory: Normal Forms And All That Jazz (Theory In Practice), By C. J. Date, exactly how can you haggle with the many things that has lots of perks for you?
Database Design and Relational Theory: Normal Forms and All That Jazz (Theory in Practice), by C. J. Date
PDF Ebook Database Design and Relational Theory: Normal Forms and All That Jazz (Theory in Practice), by C. J. Date
Database Design And Relational Theory: Normal Forms And All That Jazz (Theory In Practice), By C. J. Date. In what situation do you like reviewing so a lot? What concerning the kind of guide Database Design And Relational Theory: Normal Forms And All That Jazz (Theory In Practice), By C. J. Date The have to read? Well, everybody has their very own reason why needs to check out some e-books Database Design And Relational Theory: Normal Forms And All That Jazz (Theory In Practice), By C. J. Date Primarily, it will associate with their necessity to obtain knowledge from the book Database Design And Relational Theory: Normal Forms And All That Jazz (Theory In Practice), By C. J. Date as well as intend to read merely to get home entertainment. Stories, story e-book, as well as other enjoyable publications become so preferred today. Besides, the scientific e-books will likewise be the most effective factor to choose, especially for the pupils, educators, doctors, business owner, and various other occupations that are warm of reading.
As understood, many individuals say that publications are the home windows for the globe. It doesn't suggest that purchasing e-book Database Design And Relational Theory: Normal Forms And All That Jazz (Theory In Practice), By C. J. Date will mean that you can get this world. Merely for joke! Reviewing an e-book Database Design And Relational Theory: Normal Forms And All That Jazz (Theory In Practice), By C. J. Date will opened up a person to believe far better, to maintain smile, to delight themselves, as well as to encourage the understanding. Every book likewise has their particular to influence the viewers. Have you understood why you review this Database Design And Relational Theory: Normal Forms And All That Jazz (Theory In Practice), By C. J. Date for?
Well, still perplexed of exactly how to obtain this book Database Design And Relational Theory: Normal Forms And All That Jazz (Theory In Practice), By C. J. Date below without going outside? Just link your computer or kitchen appliance to the net and start downloading and install Database Design And Relational Theory: Normal Forms And All That Jazz (Theory In Practice), By C. J. Date Where? This page will certainly show you the link page to download and install Database Design And Relational Theory: Normal Forms And All That Jazz (Theory In Practice), By C. J. Date You never ever stress, your favourite book will certainly be quicker your own now. It will certainly be a lot easier to delight in reviewing Database Design And Relational Theory: Normal Forms And All That Jazz (Theory In Practice), By C. J. Date by on-line or getting the soft documents on your gizmo. It will regardless of which you are as well as what you are. This publication Database Design And Relational Theory: Normal Forms And All That Jazz (Theory In Practice), By C. J. Date is composed for public as well as you are among them who could delight in reading of this e-book Database Design And Relational Theory: Normal Forms And All That Jazz (Theory In Practice), By C. J. Date
Spending the downtime by reading Database Design And Relational Theory: Normal Forms And All That Jazz (Theory In Practice), By C. J. Date can supply such fantastic encounter also you are only seating on your chair in the office or in your bed. It will not curse your time. This Database Design And Relational Theory: Normal Forms And All That Jazz (Theory In Practice), By C. J. Date will certainly assist you to have more priceless time while taking remainder. It is really enjoyable when at the midday, with a mug of coffee or tea and a publication Database Design And Relational Theory: Normal Forms And All That Jazz (Theory In Practice), By C. J. Date in your kitchen appliance or computer monitor. By delighting in the sights around, right here you can begin checking out.
What makes this book different from others on database design? Many resources on design practice do little to explain the underlying theory, and books on design theory are aimed primarily at theoreticians. In this book, renowned expert Chris Date bridges the gap by introducing design theory in ways practitioners can understand—drawing on lessons learned over four decades of experience to demonstrate why proper database design is so critical in the first place.
Every chapter includes a set of exercises that show how to apply the theoretical ideas in practice, provide additional information, or ask you to prove some simple theoretical result. If you’re a database professional familiar with the relational model, and have more than a passing interest in database design, this book is for you.
Questions this book answers include:
- Why is Heath’s Theorem so important?
- What is The Principle of Orthogonal Design?
- What makes some JDs reducible and others irreducible?
- Why does dependency preservation matter?
- Should data redundancy always be avoided? Can it be?
Databases often stay in production for decades, and careful design is critical for avoiding subtle errors and processing problems over time. If they’re badly designed, the negative impacts can be incredibly widespread. This gentle introduction shows you how to use important theoretical results to create good database designs.
- Sales Rank: #244850 in Books
- Published on: 2012-04-27
- Released on: 2012-04-27
- Original language: English
- Number of items: 1
- Dimensions: 9.19" h x .70" w x 7.00" l, .95 pounds
- Binding: Paperback
- 278 pages
Most helpful customer reviews
34 of 36 people found the following review helpful.
Nobody teaches normalization any more!
By Amazon Customer
You ought to know who Chris Date is. Return with me now to those thrilling days of yesteryear (the late 1970's, early 1980's) when RDBMS has just been created by Dr. E. F. Codd. The problem was that Dr. Codd was a mathematician whose earlier work was with self-reproducing cellular automata. He wrote and thought like a mathematician, not a programmer. His notation was abstract and mathematical. He used standard set operators for Union, Intersect, Set Difference, membership and so forth. Projections (SELECT in SQL) was shown with a letter pi (�) with subscript parameters, the selection (FROM in SQL) was shown with a letter sigma (�) with subscript parameters and he invented the butterfly or bow ties for joins. In short, nobody could read it unless they were a math major. We did a lot of work with this notation and if you like curling up with a glass of sherry and a warm calculus book, the best mathematical book on RDBMS is still Theory of Relational Databases by David Maier (Mar 1983, ISBN: 978-0914894421).
But the real problem was not that the early papers were academic. When the first SQL products came out, RDBMS was like pre-teen sex. Everyone claimed that they knew what it was and that they were good at it. Yeah. Right. Chris Date and Dr. Codd formed a consultancy to educate the world. Dr. Codd was the brains and the big name; Chris Date was the "Great Explainer" who wrote magazine articles and gave lectures. People could understand Chris Date! His INTRODUCTION TO DATABASES was a standard college textbook in the early days of RDBMS. His collections of columns in DBMS and DATABASE PROGRAMMING & DESIGN should be part of any RDBMS library.
Date has since written a lot of books on databases for many different publishers. But even today, his sample database of Suppliers who provide Parts for Jobs is referred to by the name "SPJ" in the literature. Chris Date does not like SQL and writes his books in a language called Tutorial D. This language is directly based on Relational Algebra and Relational Calculus. You can find more about it at [...]. But you do not need to know this language to read the book; the code used is obvious and can quickly map into SQL when an equivalent SQL code is not given.
If you think you know enough about Normal Forms and all that jazz, then you are wrong. I was. Date is back to being "The Great Explainer" again. He has a running examples thru the whole book that use simple, small data base schemas. He does not assume you are a math major, but just a working programmer who needs to be grounded in real work to get to the theory.
The chapters come in pairs; the first is an informal look at the topic, the second is more formal explanation. For example: Chapter 4 is "FDS and BCNF (Informal)" then Chapter 5 is "FDs and BCNF (Formal)" and that pattern continues in the rest of the book. When you get bogged down in the formal stuff, go back to the previous section. Each chapter ends with exercises; do not worry, there are answers in the back of the book. Chris has written too many textbooks, and a lot of his exercises are really discussion questions.
Keys are discussed in detail and he demolishes the surrogate key concept. Then he spends all of chapter 8 debunking the myths of denormalization. Yes, people still do it after all this time.
Do you know the two purposes Normalization serves? I think of it as a method (not the only one) to reduce redundancy in a schema. But it can also correct a bad design. These are two distinct problems, but people get them confused. I am now thinking of which normal form I need from the hierarchy before I design a schema instead of a clean up after the first design.
Seeing the current Normal Form Hierarchy made me feel like I had not kept up with my reading. The few SQL programmers that even know what a Normal Form is at all, think that it is "First Normal Form (1NF) is flat files", they have no idea about Second Normal Form (2NF), think that "Third Normal Form (3NF) is when I declare some column as PRIMARY KEY, and I am done" and they have no idea about other normal forms at all.
Date gives a list of the following nine Normal Forms. Then he shows how something can be in one Normal Form and is by implication in all the lesser Normal Forms, but not in any of the higher Normal Forms.
1NF = First Normal Form
2NF = Second Normal Form
3NF = Third Normal Form
BCNF = Boyce-Codd Normal Form
4NF = Fourth Normal Form
RFNF = Redundancy Free Normal Form
SKNF = Superkey Normal Form
5NF = Fifth Normal Form
6NF = Sixth Normal Form
But this is not all of them! We also have Elementary Key Normal Form (EKNF), Complete Key Normal Form (CKNF) and Domain Key Normal form (DKNF) as well.
You get a simple introduction to Functional Dependencies (FD) and Multi-Valued Dependencies (MVD) and the algebra that goes with them. This how we can safely get rid of redundant tables in a schema and know with mathematical certainty we have not lost data.
There are also a lot of discussion of practical considerations. Let me throw out one example for your to play with, re-written in SQL:
CREATE TABLE Payments
(cust_nbr INTEGER NOT NULL
REFERENCES Customer_Accounts (cust_nbr),
payment_date DATE NOT NULL,
PRIMARY KEY (cust_nbr, payment_date),
payment_amt DECIMAL (10,2) NOT NULL
CHECK (payment_amt > 0.00))
CREATE TABLE Customer_Accounts
(cust_nbr INTEGER NOT NULL PRIMARY KEY,
payment_amt_tot DECIMAL (10,2) NOT NULL
CHECK (payment_amt_tot > 0.00));
The business rule is that account balance agrees with the sum of the payments:
CREATE ASSERTION Correct_Balances
CHECK
(NOT EXISTS
(SELECT *
FROM (SELECT A.cust_nbr, A.payment_amt_tot,
SUM(P.payment_amt)
OVER (PARTITION BY P.cust_nbr) AS P_amt_tot
FROM Customer_Accounts AS A, Payments AS P
WHERE P.cust_nbr = A.cust_nbr)
WHERE P_amt_tot A.payment_amt_tot));
The Customer_Accounts table is clearly redundant, since it is all derived data. There are four possible ways to handle this.
1) Ignore the problem and do not write the constraint. You see this "solution" all too often. And then someone tries to fix it in the application layers of the system.
2) Declare the constraint. This happens to be harder in T-SQL because we do not have a CREATE ASSERTION statement. You might try using Triggers, but what happens when someone monkeys with the Customer_Accounts directly without waiting for a trigger to fire in the Payments table?
3) Create a VIEW. But the user has to know that he cannot touch the Customer_Accounts
4) Create a snapshot. Now the user can touch the Customer_Accounts, but that this is dangerous for data integrity.
So, how would you fix it? And why?
34 of 38 people found the following review helpful.
I couldn't read it.
By Alexei Lebedev
Mr. Date has a wandering style of presentation that I find impossible to follow. Most statements either state that an earlier definition was not strictly speaking, correct, or a promise to say more on the subject in another chapter. Every sentence has parenthetical asides or begins with decorations such as "Note, carefully, however"; "Now, we might say, very loosely, that..."; "However there is a significant difference also."; "In order to understand this state of affairs a little better, it's helpful to go back to..."; "As an aside, I note that the foregoing discussion goes a long way toward..." etc. etc. etc. Every definition is "preliminary",
Some examples:
Exercise 2.1 is "What's the Information Principle?" -- a seemingly important question. The information principle is not discussed in chapter 2 at all. The answer in given in Appendix D: "The Information Principle is a fundamental principle that underpins the entire relational model." Shouldn't perhaps Chapter 1 begin with this definition?
Here is a paragraph from Chapter 3 whose only purpose seems to be to reference a concept from Chapter 1 and delegate it to Chapter 15:
"In chapter 1, I said design theory is largely about reducing redundancy, and I've referred to the concept repeatedly in the present chapter; in particular, I've said the higher the level of normalization, the more redundancy is prevented. But coming up with a precise definition of redundancy seems to be quite difficult -- much more so, in fact, than I think is appropriate for this early point in the book. For that reason, I'm not even going to try to define it here; I'm just going to assume until further notice that we can at least recognize it when we see it (though even that's a pretty big assumption, actually). Chapter 15 examines the concept in depth".
I learned more from Codd 1970 paper and wikipedia article on normal forms.
11 of 11 people found the following review helpful.
Database Design and Relational Theory: Normal Forms and All That Jazz
By J. W. Rine
C. J. Date is an independent author, lecturer, researcher, and consultant specializing in relational database theory. My introduction to his work came while I studied the Php/SQL course series online via the O'Reilly School of Technology. I received a copy of Database in Depth: Relational Theory for Practitioners, ISBN 0-596-10012-4, to accompany the online coursework. A couple of chapters into Database Design and Relational Theory I stopped and read again the aforementioned Database In Depth as a refresher.
Database Design and Relational Theory: Normal Forms and All That Jazz is about the logical design of a database as it relates to the relational data model. It's about the theory of the relational model and the accompanying algebra. These concepts are separated from physical design as physical design relates to how a particular logical design will map to actual physical storage.
The book is written for an audience accustomed to the terminology and concepts of the relational model. Definitions are introduced moving from the informal to the formal. Throughout the book the discussion involves relations, relvars, tuples, functional dependencies, join dependencies and various algebraic operators. If all this seems foreign, then I would suggest another text to be read as prerequisite to this book. Admittedly, I do not have a background in computer science or mathematics. I found the material difficult at times but not overly so. I think that after reading this book I have a much better grasp on normalization when it comes to creating my own database.
I would recommend this book to those readers with a desire to learn about relational design theory. It is product agnostic with mentions of SQL limited to instances where SQL breaks from the relational model. It is an advanced text and requires thought and concentration commensurate to the fields of computer science and mathematics.
Disclosure: I recieved a free ebook copy for review purposes.
Database Design and Relational Theory: Normal Forms and All That Jazz (Theory in Practice), by C. J. Date PDF
Database Design and Relational Theory: Normal Forms and All That Jazz (Theory in Practice), by C. J. Date EPub
Database Design and Relational Theory: Normal Forms and All That Jazz (Theory in Practice), by C. J. Date Doc
Database Design and Relational Theory: Normal Forms and All That Jazz (Theory in Practice), by C. J. Date iBooks
Database Design and Relational Theory: Normal Forms and All That Jazz (Theory in Practice), by C. J. Date rtf
Database Design and Relational Theory: Normal Forms and All That Jazz (Theory in Practice), by C. J. Date Mobipocket
Database Design and Relational Theory: Normal Forms and All That Jazz (Theory in Practice), by C. J. Date Kindle
Tidak ada komentar:
Posting Komentar