Question

When working with tables in Oracle, how do you know when you are setting up a good index versus a bad index?

Answer 1

This depends on what you mean by ‘good’ and ‘bad’. Basically you need to realise that every index you add will increase performance on any search by that column (so adding an index to the ‘lastname’ column of a person table will increase performance on queries that have ‘where lastname = ‘ in them) but decrease write performance across the whole table.

The reason for this is when you add or update a row, it must add-to or update both the table itself and every index that row is a member of. So if you have five indexes on a table, each addition must write to six places – five indexes and the table – and an update may be touching up to six places in the worst case.

Index creation is a balancing act then between query speed and write speed. In some cases, such as a datamart that is only loaded with data once a week in an overnight job but queried thousands of times daily, it makes a great deal of sense to overload with indexes and speed the queries up as much as possible. In the case of online transaction processing systems however, you want to try and find a balance between them.

So in short, add indexes to columns that are used a lot in select queries, but try to avoid adding too many and so add the most-used columns first.

After that its a matter of load testing to see how the performance reacts under production conditions, and a lot of tweaking to find an aceeptable balance.