Multi provider query performance

[Former Member]

I have created a multi provider which was originally a copy of an existing multi provider - I have replaced one of the info cubes with a different multi provider in the copy version. At present there is just a requirement to build one query off the multi provider. This requires a much smaller subset of characteristics to be identified in the multi provider compared to the original multi provider. How much impact does identification of more than required characteristics (I require 50 and at present there are 190) have on query performance? Thanks

[Former Member]

Hi:

If this is the case, I would try to go for an BI Aggregate, which is a better way to take only what a user needs from a larger structure.

Kind regards.

[Former Member]

Niten,

I differ a bit here. Though there wont be much impact on the performance, but there will be some impact ofcourse. In case of MP, the OLAP processor has to divide a query in many sub-query which ultimately gets executed. When you will have large identification, the OLAP processor will take slighty higher time.

Thanks..

Shambhu

[Former Member]

Thanks guys.

Shambhu, to be honest I was thinking along the same line as you but than what is swaying me otherwise is that I feel (which I am not sure on) that the identification indicates the union between objects which are part of the multi provider structure at the database level. Therefore when I define my query with the 50 or so info objects the performance would be specific here. This is just my theory though

[Former Member]

That should not be a problem. You can go ahead. Anyhow you the subset is very less compared to teh existing one. Again reporting on multiprovider for better performance is recommended now....

[Former Member]

Hi Niten,

I dont think that u will get poor query performance if u select more than what u require from the MP..

Selecting more fields in Multiprovider will allow u to take the more number of objects in ur query.. as long as the query is using the less number and the query will also look for the values which it is looking for...

So u can very well design ur MP will more objects in that.. I dont think that u will endup with the poor query performance..

Thanks

Hope this helps