- Hardcover: 328 pages
- Publisher: Wiley-Interscience; 1 edition (July 7, 2005)
- Language: English
- ISBN-10: 0471719994
- ISBN-13: 978-0471719991
- Product Dimensions: 6.4 x 0.8 x 9.6 inches
- Shipping Weight: 1.2 pounds (View shipping rates and policies)
- Average Customer Review: 7 customer reviews
- Amazon Best Sellers Rank: #1,130,347 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.
Relational Database Index Design and the Optimizers 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
Customers who viewed this item also viewed
Customers who bought this item also bought
"I recommend this book to all those who have anything to do with database performance. It is a must-read for all database administrations, database designers, performance-tuning specialists, and application programmers…" (Computing Reviews.com, November 20, 2005)
From the Back Cover
Improve the performance of relational databases with indexes designed for today's hardware
Over the last few years, hardware and software have advanced beyond all recognition, so it's hardly surprising that relational database performance now receives much less attention. Unfortunately, the reality is that the improved hardware hasn't kept pace with the ever-increasing quantity of data processed today. Although disk packing densities have increased enormously, making storage costs extremely low and sequential read very fast, random reads are still painfully slow. Many of the old design recommendations are therefore no longer validthe optimal point of indexing has come a long way. Consequently many of the old problems haven't actually gone awaythey have simply changed their appearance.
This book provides an easy but effective approach to the design of indexes and tables. Using lots of examples and case studies, the authors describe how the DB2, Oracle, and SQL Server optimizers determine how to access data, and how CPU and response times for the resulting access paths can be quickly estimated. This enables comparisons to be made of the various designs, and helps you choose available choices for the most appropriate design.
This book is intended for anyone who wants to understand the issues of SQL performance or how to design tables and indexes effectively. With this title, readers with many years of experience of relational systems will be able to better grasp the implications that have been brought into play by the introduction of new hardware.
Try the Kindle edition and experience these great reading features:
There was a problem filtering reviews right now. Please try again later.
The book gives a closer look at indexes generically means one size fits all databases view point. In reality some database products since have much evolved such that the examples given in some chapters on real world index tuning dramas in mainframe era have become a thing of the past.
The latest RDBMS product shows such index issues by a simple right click by a lame duck person on a slow query issue. And it may also suggest adding a new index or modifying an existing index to the pin point or closer HOW GOOD is THAT? This just really surprised me a lot.
Also the book targets two different dominant database products in the market. Some of the concepts and points are just too hard to decipher may be because it sort of biased on Oracle reader? The book is certainly not for the SQL server beginner designers.
If the book is based on a particular database product say Oracle or SQL Server it would have definitely be a winner for a larger segment of readers out there mainly concentrating on one product. It is highly unlikely large enterprises use both products!!!
Again a generic book for the two dominant database products may not be useful as SQL Server is what I use and some of the features like index book marking look up etc. and SQL profiler under the hood query optimization techniques adds so much to the equation that we are trying to solve.
Also have to mention the example codes what they meant for? All are coded using cursors it is just a bit 'off the track' of real world situations as cursors are discouraged. If the answer is the cursors are used to highlight a pure indexing point then sadly the moment the cursor was dropped and re-designed the query then SQL server brings in all the other profiler based query tuning variables.
Apart from the above issues I spent a lot of time reading and grabbing 'basics' of index design. It was hard for me though I managed to get some ideas from this book into production. And searching through Amazon for similar books it is only this book I found that trying to isolate indexing as a separate entity from whole database design and query design subject. This reason is why I am giving it a four star.
The book takes a very pragmatic approach to speeding up SQL SELECTs, it's all about making SELECTs fast. One more thing to notice about this book is that authors talk about tables that contain tens of millions of rows and queries that could take hours (or forever) in the worst case. Compare this to some other SQL performance optimization books that talk about tens of thousands of rows. Sure there is a huge difference in approaches.
Now, why SELECTs could be slow ? Surprise, huge data volume plus limited hardware capacity. How to overcome this ? Surprise, by proper indexing. We all know that.
But ! What exactly a good index is, how to build a good index or improve an existing one, how to estimate the quality of an existing index, how to estimate the query execution time with this or that access path, how the optimizer chooses its ways, which predicates affect it's decisions in which way, how to monitor the database activity and determine what to improve, how indexes wear out with time - this book discusses in a very simple, clear and pragmatical way.
The book gives a clear view of the current state with indexing relational databases. It shows you the principles but does not give any rules of thumb, you still have to understand what you are doing and what are the implications, rather than blindly following the textbook.
And it seriously shifts the way you look at indexes, at least it was so in my case.
This is an invaluable book, but it should be accompanied with a good and very deep tuning guide for your own database of choice. If read alone, it leaves you empty handed, because you wouldn't know where to look in your own database. And if that other guide is not deep enough, it would be a useless companion.
An amazing book for a thinking DBA.
If you are a DBA who think you already read everything worth to know about indexing, don't miss this book.
The authors don't try to sell you any simplified tricks.
The book describes a solid methodology, how to diagnose the performance problems and how to do proactive and reactive tuning.
The text is dense, but it makes sense. The examples are clear.
In addition to the actual DBA work, the book builds up an idea of a quality assurance system. In principle, the software developers could be tought a reasonable set of rules-fo-thumb. The goal is to avoid the worst performance pitfalls.
Index design is not easy, especially when there are many tables involved, joined together in a variety of interesting ways. However, this book helped me understand the core issues of index design. It also helped me understand how to estimate the cost of different indexing strategies. Throughout the book, the authors did a good job of being consistent in their treatment of the topic. I am armed, ready to tackle my report performance issue!