Skip to Content
author's profile photo Former Member
Former Member

Universe Designer Queries

Hi Everyone,

I have following two queries regarding universe designing:

1. Do we need inexes created in the database in order to use the index awareness in universe designer Or we can use index awareness even when there are no indexes created in the database?

2. Can we use objects from different classes when creating custom hierarchies?

Regards,

Neeraj Sharma

Add a comment
10|10000 characters needed characters exceeded

Related questions

5 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Sep 02, 2013 at 08:30 AM

    Index awareness is pointless without a correct indexing strategy within your database. If you are working with a dimensional model (i.e. a star schema - a typical data warehouse model) then the common indexes are:

    Index all join columns

    Index columns commonly used in where clauses

    Index columns commonly used in group by clauses

    That's just one aspect of performance though.

    The fastest join is an inner join on indexed integer columns.

    If you join on dates and one or both join columns use a function, an index won't help as much as creating a surrogate key for the date columns.

    Have a read up on data warehouse indexing strategies to get a more in-depth understanding of what you're indexing, as well as looking into other areas such as aggregates and partitioning. to get a fuller picture.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 30, 2013 at 02:21 PM

    Hi Neeraj,

    1. Index awareness will only help in using or making the best use of indexes created on the database.

    Index awareness in universe just help the query aware that there are indexes between the joining columns in the table, which changes the behavior of the query.

    This only works when you apply those objects in report query filters.

    Index awareness will not work if you are not using those objects in query filter(where condition).(This basically avoids join condition in the query by using the indexed table, mentioned in object properties in universe)

    2. Yes,you can create custom hierarchies in the universe using objects from different classes,but it should have a meaning to that.

    For eg. A custom hierarchy created with object YEAR,QUARTER,CUSTOMER,PRODUCT, does not make any sense when you drill from quarter to customer to product.

    Thanks

    Gaurav

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on May 10, 2013 at 12:29 PM

    Hi Neeraj,

    1. In general, if you use index awarenes on any column then the functionality will be useful if the same has been defined at the database(DB) end. for e.g,this is by-default for a primary key column. However, if you define index awareness on a column at universe-end that is not made indexed at DB-end then this feature will be redundant.

    2.Yes, if they are compatible, meaning, they fall into same context.

    -Prathamesh

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on May 10, 2013 at 05:28 PM

    HI Neeraj,

    1)if you are using the index in the Database that is more enough in the universe level, no need to use index awareness in the universe level and more over it save the performance also it is not suggestible one.

    2)you can use the custom hierarchies from different classes, but everything depends upon your DATABASE Design.

    Hope it help your query i think

    Arun.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on May 21, 2013 at 02:33 PM

    Hi Neeraj,

    1- No need. Please note that ONLY appropriate indexs at DB level depending on your DB.

    2-Yes if they are compatible

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.