Dose Perspective to an extent improve the cube process performance?

Hi, all experts here,

Thank you very much for your kind attention.

Would please any expert here give me any guidance and advice that if a Perspective of a cube really improve the performance of the process in terms of process speed.

Thank you very much in advance for any guidance and advice for that.

With best regards,

Yours sincerely,

Perspectives don't affect cube processing in one way or another. Think about Perspective vs. Cube as about View vs. Table.|||

Hi, Mosha, thank you very much for your guidance.

So is it in a way like views for tables make retriveving data faster from a perspective rather than a large cube as what views meant to tables. Dose that sense perspective mean to cube (besides in a way to well organize information in cube for specific perspective)? Thanks a lot.

With best regards,

Yours sincerely,

|||Retrieving data from perspective will have exactly same performance as retrieving data from the cube. Perspective is mostly just a way to hide some dimensions/measures/actions/calculated members to have less cluttered and more focused view on the cube. But all the queries go against the cube.|||

Hi, Mosha, thank you very much for your guidance.

With best regards,

Yours sincerely,

Dose it make sense to create indexted views on a single table?

Hi, all experts here,

Thank you very much for your kind attention.

I am wondering if there is any sense to create indexed views on single table? I simple want to improve the report query performance as most of the reports data are from a single table. As views most of the time are created as for joined across tables.

Thank you very much for your advices and I am looking forward to hearing from you shortly.

With best regards,

Yours sincerely,

H Helen,

Theres is no point creating a indexed view with a view that has the columns from single table.

Infact, you will creating an overhead on your transactions as they will have to keep the indexes on view upto date on top the indexes on the table.

regards

Jag

|||

Hi, Jag,

Thank you very much for your advices and kind help. It's been very helpful.

With best regards,

Yours sincerely,

|||

Jag,

What if the single table was a transaction table, and the view was an aggregation of that transaction table.

I was under the impression that that was one of the primary reasons to utilise Indexed Views, that the aggregated data is available without having to transverse the underlying table rows, therebye improving query performance.

Cheers,

Will

|||

i would agree with Will ... though the view is refering single table... if this view is aggregation and the table is having millions of records, it make sense that you may create indexed view.

Madhu

|||

Hi Will,

You are right, if view is going to be storing aggregated data, then It is worth creating an index on a view even if is a single table.

regards

Jag