Speeding Things Up with Indexing

Yes, indeed!

Indexing seems to be a promising solution.

Jab!

An index like one at the end of a book?

Princess...I don't really care.

Let's discuss our marriage, instead.

Under the entry for transaction, pages that discuss transactions are listed.

transaction

transaction

Index

Reference page

If you create indexes for Product codes,

you can instantly learn where product data is stored for a product assigned Product code 101.

Data

It tells you where on the disk that product data is located.

Indexing helps speed up the search.

Shall I repeat the explanation from the start?

No,

no...

Well, it's not

so easy for me

to follow....

anyway...

It is very time consuming to browse all rows when searching for certain data.

Hey! Who are you talking to?

Ha, ha,

Just talking Tico ha to myself!

Oops, Raminess

can't see her.

Now, everybody,

in a standard database, I understand it is up to the database

administrator to add indexes.

Is that

On the other hand, right? creating too many

indexes may lead to inefficiency.

You see, it's like this. Suppose a book had an excessively large number of indexes. It would

be like putting the cart in front of the horse, wouldn’t it?

Furthermore, when updating data, you must update your indexes as well, and it would be all the more time consuming.

So is an index good or bad?

Well, that's how it works.

psst psst

Ha, ha!

I see.

The database is more clever than I thought.

Where did that rose come from?

The database...

What if the system on which the database is running goes down due to power failure?

Data

Doom

Data

It's not supposed to impress me like this! It has other problems, too!

No problem.

Just like that.