Multiprovider should be always created for Infocubes? Even for 1 Infocube?

[Former Member]

I was told that even if there is 1 infocube, I should still create a MultiProvider for that 1 InfoCube, because it is in theory good practice.

Is this a business norm? Is it bad practice to goto Query Designer and just open Infocube?

If this is true, can someone explain the logic behind this?

Thanks in advance.

[Former Member · Accepted solution]

It is a good idea to Create an MP (MultiProvider) on the top of several InfoCubes. This improves performance. However, building a MP on a single InfoCube does not do much on performance but it saves a lot of additional admin that may be required in future to get adapt with. See the web log below for more clarity...

https://weblogs.sdn.sap.com/pub/wlg/10148?page=last&x-order=date [original link is broken] [original link is broken] [original link is broken]

In my view, no matter whatever the number of InfoProviders are, if there is a scope to build an MP, we should do so.

[Former Member]

Thank you so much SDNBI and Larka.

😃

[Former Member]

I beleive that it's a good practice to build a multicube for reporting even if there is only one cube in it because later on ther reporting requirements may change and you may need another cube (with another set of data\different applicationb even) to enchance your reports.

In other words building queries on multicubes instead of cubes offers more flexibility later on/ you can basicaly do whatever you want with underlaying cube\cubes - include\exclude\modify anything you want.