Why do indices on HANA only consist of one column without Client-Field?

[master1980]

Hello,

I have to Create an Index in Table LIPS. All existing SAP-provided-indices only consist of one column without Client-Field.

So I have done it the same way but i dont understand it at all. Can you provide an explanation (good referenece to an Explanation) why on Hana-DB I have to create the Index without Client and only 1 column?

Many Thanks

Alexander

[Yogananda]

master1980

The reason why SAP provides indices that consist of only one column and no client field is that it is a more efficient and effective way of indexing data. This is because the index will only include the data that is necessary for the query to be processed quickly. Having multiple columns and a client field in an index would mean that the index would need to include more data than necessary, which could slow down query processing.

If this response answers your query, please accept it and close the thread.
Have a wonderful day!

[AlexanderLim]

Hi yogananda,

Is there an illustration to show how much system memory/performance we are saving by removing MANDT in the scenario where our system has only 1 MANDT.

I am wondering how worth it is to make the change compared to risk/impact in changing something that is working fine.

For example if I have table Table1 with index MANDT + COLUMN1 with 100million entries, how much the advantage/saving in system performance/memory by modifying the index to have only COLUMN1 (removing MANDT).

If the saving is for example a mere miliseconds of performance or few megabytes of memory, not sure if we want to take the risk affecting running operational data by modifying the index, adjusting the table, etc.

Appreciate your advise, Thanks.