Foxhound is the better* Database Monitor for SQL Anywhere.
*better: More thorough, more relevant, more effective.
...more Alerts, more All Clears, more details, more control in your hands.
|
[Home] | [Table of Contents] | [Previous Section] | [Next Section] |
Breck Carter
Last modified: February 12, 1998
mail to: bcarter@bcarter.com
The Rule of Thumb says "Don't create more than half a dozen indexes for a single table" but what if you really, really need indexes on every column in a huge table? Well, if it's a read-only table then go ahead, all you care about is optimizing queries. But if the table is updated as well as queried then you must understand that extra indexes will slow things down. That's when this Rule of Thumb kicks in: "If you create an index make sure you need it, and then make sure it helps where it should and doesn't hurt too much elsewhere."
Figure 21 shows that you do pay a price for multiple indexes but after the first few indexes the effect is more or less linear rather than exponential. In other words, you pay for what you get.
Figure 21 - UPDATE Slowed by Multiple Indexes
|
[Home] | [Table of Contents] | [Previous Section] | [Next Section] |