Indexing ODS

[Former Member]

BW Experts,

I have a ODS which has 2 field as key. I would like to know if this ods table is automatically indexed or is there a way to index the ODS.

Thanks

Ashwin

[former_member188975 · Accepted solution]

Hi Ashwin,

Have you seen this thread:

Pizzaman is excellent with "index" knowledge and you can also search and read other posts by him.

Hope this helps...

[Former Member · Accepted solution]

Thanks Bhanu,

I will look into Pizzaman's posts. Well The key to ODS is Doc Number and Item. This acts as a primary key to the table too. So there is no point building an index with the same fields rite. Anyways it wont be a change in performance because the primary key to the table and the index will be the same....correct me if I am wrong?

Thanks

Ashwin

[former_member188975 · Accepted solution]

Hi Ashwin,

The primary index is created automatically when the table is created in the database. The primary index contains the key fields of the table and a pointer to the non-key fields of the table. You create secondary indexes if required.

Hope this helps...

[Former Member]

Hello,

I am having performance issue with my ODS.

Right now my key fields are: source system, po doc # and item #.

My queries always have defaulted in the selection criteria: doc type; plant; calendar month and restricted as filter by item deletion flag.

Question: should i create an index with all the mentioned fields? or create more than 1 index spliting the mentioned fields?

Please can I have your advise on this?

Thanks.

Cesar

[edwin_harpino]

hi Ashwin,

you are right, keyfield(s) of ods will be the primary index, so the sequence of the keyfields is very important in reporting from that ods.

you can check if there is index for this ods with se11,

click 'indexes'. additional index can be created in ods maintainance, node indexes, create and then drag the infoobjects. indexes discussed in bw360 course.

hope this helps.

from bw360 course

Indexes on tables can help to improve the reading performance for all types of reading described above.

The order of the key fields determines the order of the fields for the primary index. The fields most frequently used for selection should be first in the order.

Additional indexes can be defined for other reading accesses, for example:

Calendar month for selective deletion / archiving

Sales Document number for reporting

In transaction DB05, you can determine the selectivity (distinct values) of table fields (single fields as well as fields in combination) and the distribution of field values. This information helps to define suitable indexes.

More information about indexes can be found in the indexes unit.

.... too late in reply

Message was edited by: A.H.P