Buy New
$36.87
Qty:1
  • List Price: $39.95
  • Save: $3.08 (8%)
Usually ships within 2 to 4 weeks.
Ships from and sold by Amazon.com.
Gift-wrap available.
Add to Cart
Have one to sell?
Flip to back Flip to front
Listen Playing... Paused   You're listening to a sample of the Audible audio edition.
Learn more

Practical Issues in Database Management: A Reference for the Thinking Practitioner Paperback

ISBN-13: 078-5342485554 ISBN-10: 0201485559 Edition: 1st

Amazon Price New from Used from Collectible from
Paperback
"Please retry"
$36.87
$7.24 $1.19

Free%20Two-Day%20Shipping%20for%20College%20Students%20with%20Amazon%20Student



Customers Who Viewed This Item Also Viewed

NO_CONTENT_IN_FEATURE

Sell Us Your Books
Get up to 80% back when you sell us your books, even if you didn't buy them at Amazon. Learn more

Product Details

  • Paperback: 288 pages
  • Publisher: Addison-Wesley Professional; 1 edition (June 2, 2000)
  • Language: English
  • ISBN-10: 0201485559
  • ISBN-13: 978-0201485554
  • Product Dimensions: 9.2 x 7.3 x 0.6 inches
  • Shipping Weight: 1.1 pounds (View shipping rates and policies)
  • Average Customer Review: 4.1 out of 5 stars  See all reviews (18 customer reviews)
  • Amazon Best Sellers Rank: #1,391,090 in Books (See Top 100 in Books)

Editorial Reviews

From the Back Cover

"The aim of this book is to provide a correct and up-to-date understanding of--and appreciation for--the practical aspects of crucial, yet little-understood core database issues. It identifies and clarifies certain fundamental concepts, principles, and techniques that persistently trouble users and vendors. It assesses the treatment of those issues in SQL (both the standard and commercial implementations) and gives specific guidance and practical advice on how to deal with them (and how not to). It covers, carefully and thoroughly, several particularly tricky and misunderstood topics--complex data types, missing information, data hierarchies, quota queries, and so forth--in a succinct and concise form for the busy database practitioner."

--C. J. Date

Three decades ago relational technology put the database field on a sound, scientific foundation for the first time. But the database industry--vendors, users, experts, and the trade press--has essentially flouted its principles, focusing instead on a "cookbook," product-specific approach, devoid of conceptual understanding. The consequences have been costly: DBMS products, databases, development tools, and applications don't always perform up to expectation or potential, and they can encourage the wrong questions and provide the wrong answers.

Practical Issues in Database Management is an attempt to remedy this intractable and costly situation. Written for database designers, programmers, managers, and users, it addresses the core, commonly recurring issues and problems that practitioners--even the most experienced database professionals--seem to systematically misunderstand, namely:

  • Unstructured data and complex data types
  • Business rules and integrity enforcement
  • Keys
  • Duplicates
  • Normalization and denormalization
  • Entity subtypes and supertypes
  • Data hierarchies and recursive queries
  • Redundancy
  • Quota queries
  • Missing information
Fabian Pascal examines these critical topics thoroughly, comparing the severe costs of mishandling them to the practical benefits of implementing the correct solutions. With an emphasis on both principles and practice, Practical Issues in Database Management employs real-world examples to provide an assessment of current technology--SQL and the DBMS products based on it--and, whenever possible, offers concrete recommendations and workarounds. With the insight provided by Practical Issues in Database Management , you will be in a far better position to evaluate specific products, exploit their capabilities, and avoid their deficiencies.

0201485559B04062001

About the Author

Fabian Pascal is an independent industry analyst, consultant, author, and lecturer specializing in database management. He is the author of two previous books, Understanding Relational Databases and SQL and Relational Basics, and has contributed extensively to many industry publications.

0201485559AB04062001


More About the Author

Discover books, learn about writers, read author blogs, and more.

Customer Reviews

This is his best book yet!
Bob Badour
This is the only book that I have found that addresses the gap between relational theory and its implementation in the real world.
Wayne Hiner
If you choose to engage, you will benefit beyond belief.
TODD A METZ

Most Helpful Customer Reviews

35 of 37 people found the following review helpful By A.M. on June 25, 2000
Format: Paperback
Contains discussions on widely misunderstood, but vitally important, database issues. Considers how things should be according to relational theory, what goes wrong in practice due to failing to understand these fundamental concepts, and provides practical recommendations/workarounds where possible. A bridge between theory and practice. A concise and straightforward read, although to gain maximum benefit you should already have a reasonable understanding of relational databases.
Some of the main points are as follows. Relational databases can support data types of arbitrary complexity ("objects") - but we need DBMS vendors to implement the means to provide such support. Use declarative integrity constraints when possible. Avoid tables that allow duplicate rows - ensure all tables have a primary key (may require a surrogate key). Avoid redundant data. Ensure your database is normalized - avoids numerous problems. Resist the temptation to denormalize. Recognise entity supertypes/subtypes and how to implement as tables. Minimize use of nulls whenever possible. Also discusses climbing trees and quota queries. Separate chapters discuss all these points in detail.
A constant theme throughout the book is how poorly SQL and commercial DBMSs support relational concepts, and the numerous problems this causes. Personally, I believe there is little that most application/database developers can do about this, other than suffer what gets "inflicted" upon us. Pascal urges us to pressurise DBMS vendors to provide better relational support.
This book is firmly of the view that "relational is right". If you agree, you will probably like this book. Most of the references are to C.J Date's writings.
Read more ›
2 Comments Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
18 of 20 people found the following review helpful By Forrest L. Norvell on February 9, 2006
Format: Paperback
I came to this book with high hopes after having read much of Fabian Pascal's writing on the Web, which is very specific in calling out the many weaknesses of contemporary database practice and much less specific when it comes to strategies for dealing with those weaknesses. Unfortunately, the writing in this book is much like his writings online.

Pascal is clearly a seasoned professional and also someone who understands the relational model well. However, his frustration with the current state of the art bleeds over into this book, and is unhelpful. I now very clearly understand that SQL is incapable of dealing with a truly relational view of data, and that SQL (and by extension almost all contemporary DBMSes) is flawed and illogical in many ways, but there's only so much that I, as a database designer and software developer, can do with that information. In many cases, only a change in phrasing would have been necessary: I think the book would have been much more useful if it had been written prescriptively, as a "style guide" or best practices manual (DON'T use NULL. DO normalize your relations to at least 3NF) with his impassioned critiques of current technology provided as rationales for his guidelines.

Also, there's more than a whiff of the amateur to the presentation in this book. Aside from the baffling reprints of web pages included as appendices to the first chapter, he recycles exhortations across chapters and reuses the same examples over and over (down to the same explanatory text), without necessarily explaining what's different about this usage from all the others. Add to that a large, wide text face and the book, not particularly long at 256 pages, starts to feel significantly padded.

Most interested parties would be much better served by C.J.
Read more ›
1 Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
4 of 4 people found the following review helpful By Malleus Maleficarum on August 22, 2007
Format: Paperback
This is a decent book to read within the first year of your dealing with relational databases. Most chapters (particularly the ones on normalization and subtypes) are at least in some way informative and will improve your clarity of thought. Whether the book is really practical is open for discussion, since it deliberately stays away from real products, pointing to their deficiencies and suggesting you should demand improvement from the vendors. OK, I'll send letters to Gates and Ellison today. But it _is_ practical in the sense of improving your thinking on the more fundamental level. Which is nothing to sneeze at, of course.

That said, the book has a strong unprofessional taste to it in terms of overall delivery: it's really half a dozen blog entries, padded with endless recaps, intros, and even a strange assemblage of web pages whose connection to the main body of text is tenuous at best (some of them aren't even referred to! Why is this junk inserted in the book? To achieve the obligatory two-hundred-page volume?) A pile of quotes from online posts, attributionless excerpts from 'trade magazines' supposedly illustrating all-pervading imbecility of the database constituency, and so on. The points the author makes are correct, but he belabours them way too much. Where one quote would suffice he gives you five.

A fair number of typos -- nothing terrible, something like the following: say, there's a picture of a table with fields, and then in the text the fields' names are different -- no big deal, but this is a technical book and small discrepancies like that really slow you down. A couple of openly ungrammatical statements (copy editing, anyone?
Read more ›
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again

Product Images from Customers

Most Recent Customer Reviews

Search
ARRAY(0xa349c99c)