business objects - Cube vs. Micro Cube in BusinessObjects -

business objects - Cube vs. Micro Cube in BusinessObjects -

i having problems understanding cubes , microcubes in businessobjects environment. although have tried find answers online, did not find answers give overall explanations. beside description of functionality, know cube , micro cube located: on server or in browser? how many cubes/microcubes there? 1 microcube per study or 1 micro cube per session, or sthg else?

furthermore, can explain difference in aggregations on database level opossed aggregation on study level (when defining measure, there 2 possibilities - define aggregation on study and/or aggregation level). although there answers online, general. therefore, appreciate simple explanation example.

and finaly, possible color tables in info foundation layer? (since have lot of tables in universe, helpful if color fact , dimensional tables).

it helps understand two-pass nature of querying traditional (non-olap) info in bo. when refresh study in bo, study engine constructs sql statement based on objects (results , conditions) specified in query.

the sql statement sent database, , study engine retrieves info returned database. info becomes microcube -- nil more tabular representation of info received database. if @ visually, identical running sql statement in traditional sql tool (such toad or sql*plus).

the microcube becomes source study presentation. could, example, create table in study dragging in dimensions , measures object list. dragging in these objects, table recalculate , redisplay appropriate. done retrieving , calculating info microcube, not source data. is, interacting study tab, not initiating refresh database -- of calculation done microcube.

for example, let's have created new query 2 dimensions (state, region) , 1 measure (sales). sql might this:

select state_nm,region_nm,sum(sales_amt) all_sales grouping state_nm,region_nm

note there sum() applied sales_amt. causing database perform initial aggregation on field.

the microcube created after refresh may like:

al north 30000 al south 40000 ar north 5000 ar south 10000

now create table in report, , select state , sales. study engine uses info in microcube display result:

al 70000 ar 5000

in case, bo study engine has performed sum() aggregation on sales amt. report-side aggregation.

then remove state. again, study engine aggregates table microcube, not database:

75000

the microcube stored study file. if working webi study via infoview, microcube loaded server's memory. when save report, physical file created on server (with .wid extension); microcube stored in file. if open study again, microcube 1 time again loaded server's memory , available interaction.

if using rich client, same behavior applies, it's using workstation , local storage.

the term "cube" used describe info sources in olap environment (ssas or essbase, example). external bo -- bo querying info from olap cube.

business-objects