- Series: The Morgan Kaufmann Series in Data Management Systems
- Paperback: 448 pages
- Publisher: Morgan Kaufmann; 4th edition (April 4, 2007)
- Language: English
- ISBN-10: 0123693896
- ISBN-13: 978-0123693891
- Product Dimensions: 7.5 x 1 x 9.2 inches
- Shipping Weight: 2 pounds (View shipping rates and policies)
- Average Customer Review: 5 customer reviews
- Amazon Best Sellers Rank: #2,582,364 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Physical Database Design: The Database Professional's Guide to Exploiting Indexes, Views, Storage, and More (The Morgan Kaufmann Series in Data Management Systems) 4th Edition
Use the Amazon App to scan ISBNs and compare prices.
Fulfillment by Amazon (FBA) is a service we offer sellers that lets them store their products in Amazon's fulfillment centers, and we directly pack, ship, and provide customer service for these products. Something we hope you'll especially enjoy: FBA items qualify for FREE Shipping and Amazon Prime.
If you're a seller, Fulfillment by Amazon can help you increase your sales. We invite you to learn more about Fulfillment by Amazon .
See the Best Books of 2018 So Far
Looking for something great to read? Browse our editors' picks for the best books of the year so far in fiction, nonfiction, mysteries, children's books, and much more.
"I highly recommend Physical Database Design by Lightstone, Teorey, and Nadeau. The book covers fine aspects of physical design -- issues such as the effects of different approaches to indexes, tradeoffs in materializing views, and details of physical data layout. Unlike other books, it does not focus on a particular product, but instead covers the deep principles that cut across products. The book addresses both transaction intensive applications (OLTP) as well as data warehouses (OLAP). Their new book is a welcome addition to the literature." --Michael Blaha, OMT Associates, Inc.
"This is an excellent book on physical database design, giving pragmatic models and advice. It has a wealth of information for both the student and for the practitioner -- presenting analytic models and practical tips that are demonstrated with examples using Oracle, DB2, and Microsoft SQL Server." --Jim Gray, Microsoft Research
From the Back Cover
I highly recommend Physical Database Design by Lightstone, Teorey, and Nadeau. The book covers fine aspects of physical design -- issues such as the effects of different approaches to indexes, tradeoffs in materializing views, and details of physical data layout. Unlike other books, it does not focus on a particular product, but instead covers the deep principles that cut across products. The book addresses both transaction intensive applications (OLTP) as well as data warehouses (OLAP). Their new book is a welcome addition to the literature.
--Michael Blaha, OMT Associates, Inc.
This is an excellent book on physical database design, giving pragmatic models and advice. It has a wealth of information for both the student and for the practitioner -- presenting analytic models and practical tips that are demonstrated with examples using Oracle, DB2, and Microsoft SQL Server.
--Jim Gray, Microsoft Research
The rapidly increasing volume of information contained in relational databases places a strain on databases, performance, and maintainability: DBAs are under greater pressure than ever to optimize database structure for system performance and administration.
Physical Database Design discusses the concept of how physical structures of databases affect performance, including specific examples, guidelines, and best and worst practices for a variety of DBMSs and configurations. Something as simple as improving the table index design has a profound impact on performance. Every form of relational database, such as Online Transaction Processing (OLTP), Enterprise Resource Management (ERP), Data Mining (DM), or Management Resource Planning (MRP), can be improved using the methods provided in the book.
" The first complete treatment on physical database design, written by the authors of the seminal, Database Modeling and Design: Logical Design, 4th edition.
" Includes an introduction to the major concepts of physical database design as well as detailed examples, using methodologies and tools most popular for relational databases today: Oracle, DB2 (IBM), and SQL Server (Microsoft).
" Focuses on physical database design for exploiting B+tree indexing, clustered indexes, multidimensional clustering (MDC), range partitioning, shared nothing partitioning, shared disk data placement, materialized views, bitmap indexes, automated design tools, and more!
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
Basic indexing methods such as the all too common B+tree, hash table and bitmap are addressed, differences and benefits explained. Index selection methods and trade-offs are assessed in a sensible way. A useful set of rules of thumb on indexing is provided as well.
Next come partitioning and clustering techniques such as shared-nothing and hash range partitioning and MDC (Multi Dimensional Clustering). Pros and cons are provided and explained. Sound examples that illustrate the usage combinations of indexing, partitioning and clustering techniques are given.
Query optimization, plan selection and execution aspects are addressed with focus on where the indexing, partitioning and clustering techniques previously discussed fit in and on how physical design can be improved by selecting the right plan.
There is a chapter on automated database physical design that, although it does not focus much on a particular product, gives an overview of the way IBM DB2 Design Advisor, MS SQL Server Database Tuning Advisor and Oracle SQL Access Advisor handle tunings and optimizations.
Server topology, hardware aspects like CPU, memory, storage systems, performance aspects and their impacts are addressed as well.
The last two chapters are, respectively, about performance improvements through denormalization and specifics of distributed database allocation.
Here we have a useful book that covers the main aspects of physical database design and thoroughly discusses them. The book content is accessible to someone having - at least - basic database knowledge, although I found not all parts of it are easy to grasp. If you get this book, depending on your database proficiency level, you may feel like you need to read parts of it more than a couple of times to get what the authors meant to say. This is not a beginner's book: Some prerequisite knowledge on Data Modeling and on SQL is required. If not the case, better to start from there.
What I liked most in this book is the "Tips and Insights for Database Professionals" section that is located at the end of each chapter and that acts as a sort of "cookbook" summarizing the outcomes/conclusions of the chapter it relates to. Once the core of the book grasped, you can keep going by the "Tips and Insights..." only.
By the reading this book alone, the reader cannot expect to become an expert in physical database design, but there is valuable information in it that will allow the designer to be better aware of the automatic/by default performance optimization options of the actual database product he/she'll probably be using most of the time.
I identified 18 typing errors in the entire book, but nothing significant to mention.
Taking into account the above, I can easily recommend this book.
Did you ever wonder WHY heap files and B-Tree files are used in databases? This is the book to give you the why behind a lot of the lower level design decisions in databases today.
I enjoyed the why discussion of almost all of the topics, but it left me feeling a little light on the implementation. There is not much in the way of practical discussion in the book. While a discussion about index types is very well thought out it never completes the thought from an implementation standpoint. I was actually left with a lot more questions to low level implementation than I started. When to use one of these algorithms is totally left as an excercise to the reader. And in many cases the actual algorithm itself is also left to you to research. I guess they are outside the scope of the book, but I would have enjoyed it so much more with some simple pseudocode or a sample project concept to put them to use.
The book is a great reference to get you thinking about the lowest level of database implementation and make you really think about the way in which SQL Server, DB2, etc all work. But you are not left with a lot of substance on why one implementation would be better than the other for your specific application or problem domain.
RAID. Useless chapter, how you can pretend you are explaining RAID, and giving advice on what to use for RDBMS without providing comparison of protection level, overhead, R/W performance of different configurations?! The book is called "Physical database design" let me remind you.
I'm sure there should be something valuable in this book, I just haven't got to it yet.