Home > Net >  Too many composite(multi column )indexing is ok?
Too many composite(multi column )indexing is ok?

Time:01-25

Consider we have A,B,C,D,E,F,G,H columns in my table and if I make composite indexing on column ABCDE because these column are coming in where clause and then I want composite indexing on ABCEF then I create new composite indexing on ABCEF in same table but in a different query, we want indexing on column ABCGH for that i make another composite indexing in same table,

So my question is can we make too many composite indexes as per our requirements because sometimes our column in where clause gets change and we have to increase its performance so tell me is there any other way to optimise the query or we can make multiple composite indexes as per the requirements.

I tried multiple composite indexing and it did not give me any problem till now but still i want to know from all of you that will it give me any problem in future or is it ok to use only composite indexes and not single index.

Your answers will help me alot waiting for your replies. Thanks in advance.

CodePudding user response:

You can have as many as you want. However, each additional index has a cost when updating, inserting or deleting. The trick is to

  1. find common segments and make indexes for those.
  2. Or create them as required when queries are too slow.

As an example, if you are "needing" indexes for ABCDE, ABDEF, and ABGIH then create an index on just AB

CodePudding user response:

Each index requires space on the disk to be stored, and time to be updated every time you update(/insert/delete) an indexed column value.

So as long as you don't run out of storage or write operations are too slow, because you have to update too many indexes, you are not limited to create as many specific indexes as you want.

This depends on your use case and should be measured with production like data.

A common solution would be to create one index specific for your most important query e.g. in your case ABCDE.
Other queries can still use the as many columns from left to right until there is a first difference. e.g. a query searching for ABCEF could still use ABC on the previous mentioned index.
To also utilise column E you could add a where condition to D to your query in a way you know it matches all values e.g. D < 100 if you know there are only values 1-99.

  • Related