Skip to Content

Queries on ODS Objects - Improving query performance

Hi all,

In our project, we have lot of queries built on ODS objects

(will not be able change the model - so, pls do not suggest Infocubes will increase the performance - we cannot have infocubes, due to the level of detail required for reporting).

The queries have bad to poor kind of performance. I know we can create Secondary Indices on the ODS objects to improve the performance. But. the question I have is, what characteristics should we include into these secondary indices. The queries have lot of characteristics, someof them have actually crossed the allowed limit of 50 chars. - the smallest query has about 15 chars. - and we have have many navigational attributes used as well.

so how many and which characteristics should be considered for these secondary indices - ANY GUIDELINES IN CHOOSING THE CHARS WOULD BE HIGHLY HELPFUL.

thanks in advance.


Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Best Answer
    author's profile photo
    Former Member
    Posted on Aug 20, 2007 at 01:37 PM

    I found reading through this document was helpful

    Halfway down the doc theres guidance on creation of secondary indices.

    You may also want to think about reducing the number of nav attributes if possible as well as they can have a negative impact on performance.

    Message was edited by:

    Stuart Lewsey

    Add comment
    10|10000 characters needed characters exceeded