Aggregate awareness is a term that describes the ability of 
a universe to
make use of aggregate tables in a database. These are 
tables that contain
pre-calculated data. You can use a function called 
@Aggregate_Aware in the
Select statement for an object that directs a query to be 
run against aggregate
tables rather than a table containing non aggregated data.
Using aggregate tables speeds up the execution of queries, 
improving the
performance of SQL transactions.
The reliability and usefulness of aggregate awareness in a 
universe depends
on the accuracy of the aggregate tables. They must be 
refreshed at the same
time as all fact tables.
A universe that has one or more objects with alternative 
definitions based on
aggregate tables is said to be “aggregate aware”. These 
definitions
correspond to levels of aggregation. For example, an object 
called Profit can
be aggregated by month, by quarter, or by year. These 
objects are called
aggregate objects.
Queries built from a universe using aggregate objects 
return information
aggregated to the appropriate level at optimal speed.

It is an ability to dynamically rewrite sql to the level 
granularity is needed to answer business question.

Allows faster query speed.

BO Main key will store the address for repository  of the 
security domain.
General path for BOMainKey

C:\Program Files\Business Objects\BusinessObjects 
Enterprise 6\LocData

BO XI R2 provides one Migration tool along with its 
Reporting tool kit. Using this tool we can migrate 
universes from a lower version to a higher version.

BOXI is later version than BO 6.5, so all features 
available in BO 6.5 are already available in BOXI along 
with few extra features. Universe developed in BO 6.5 will 
work with no problem in BOXI. The simplest way to transport 
the universe is save the universe in BO 6.5, and open the 
universe in BOXI and save again in BOXI.

It is better to say upgrade or migrate other than transfort.
We can do this by using BOXIR2 of IMPORT WIZARD Module.
By using Import wizard,we can upgrade universes and reports 
and connections from BO5.x ,BO6.x versions to BOXIR2

Fact tables are tables with lots of measure values and are 
uniquly identified by a key, also a fact table can have a 
foreign key. For Example custumer fact table is connected 
to loan fact table via customer_id, and each record in loan 
fact table is uniquely identified by a primary key on 
cod_acct_no. Similarly customer table can be connected to 
Savings fact table through customer id.

Hi,
Heirarchies will be used in drill reports.
We will select Drilling levels in Query panel.
There are 4 types of levels are there.
1.level
2.level
3.level3
4.custom level

drill down --->navigation of levels,like one by one
drill through--->selecting new level of heirarchy at the 
time drilling
drill by--->directly selecting required drilling level

so,from your point a-b-c is drill down
a-->c is drill by 

Regards,
Arjun

Rows can be hide only when the break is applied on a 
particular column using...
Format-->Breaks-->Fold

merged dimension is nothing but to synchronize the data
from diffrent datasourcs with a common dimension

Web Intelligence allows you to synchronize multiple data 
providers in the same document. This allows you to build 
reports which synchronize data from multiple sources. When 
you synchronize queries through merging, you can include 
report objects from different queries in the same report 
block.

if we run a report it is taking so much time to display the 
result to be fallowed as :

     1) use aggrigate tables(contains pre caliculated data) 
     2)pre defined conditions,LOV's
     3)in a real time senario query contains a large if 
statements.some times we need to wait max of 30 min to run 
perticular statement...not all

If the question is not pertaining to query optimization, I 
would prefer not to use much of formatting on the page. One 
can keep the report without any page formatting as this 
would take a very long time. Try not to use the slice & 
dice panel as this would also take considerably long time...

to inprove the performence of the reports we have multiplw 
ways in my view. for example

1)generate LOV for required objects
2)use aggregate tables in universe design
3)use pre defined conditions and formulas.
4)check context (if there resolve it)
5)check loops (if there resolve it through alias table)


if u did u all these at universe level,when u generate the 
report at query panel level automatically performence will 
increese

full path client is nothing but a info-view,i think u know
abt  infoview 
1)why we go for info view 
2)what is the use

Select the object in the coss-tab, sort the object and then 
hide the object.

Go to Format--Sorts then click on Add 
vl get all the objects select the object and apply it which 
is not in the Crosstab report

While creating the report you have an "OPTIONS" tab at left 
hand side bottom. Please open that nad set the number of 
columns you need to display in the report.

We can do this in 2 levels in BO.
1.In Universe parameters,set the no of records for your 
requirements.
But I will apply to all reports.
2.We can do this to a perticular report in the query panel.
Select OPTION button(Left side down placed) and set the no 
of records how many you want.

hi,custom sorting is nothing but sorting as per our requirement
suppose months like
jan
feb
mar
apr
may
jun
jul
 we can display first jan next mar next jun
for these purpose we can use custom sort

by using allies and contexts

create alias table to resolve loops.yes

by 
alias
and contexts

By using Alias and context 

Alias- loop contains one look up table 
Context-loop contains more than one lookup table