Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
what is purpose of the loop in BO
- Thread starter bachuvenu
- Start date
Hello Bachevenu,
I suppose you mean the "loop" as described by BO in universes. The description of loop is slightly misleading, cause it has nothing to do with a loop in terms of programming (i.e. do ... while ...)
You do not choose for a loop, but in creating a universe it is quite quickly possible that tables are joined in more than one way, thus creating a loop. If you then fire an SQL at the universe, the actual path is no longer defined, there is more than one way the query can be executed (and typically, there only one good way!)
Documentation on designer gives you 2 possible solutions:
1. Create contexts
2. Create aliases
With detect loops you can check whether you need to define contexts, this is like pre-defining the path a query on the respective tables will use (i.e. the joins between tables as chosen in the SQL)
In some cases it is better to create an alias on a table (for instance if it is a lookup table , used by more than one fact-table) , thus eliminating the loop.
If you apply a context, the user can be prompted when running a report to choose from several contexts.
All of this and much more is very well documented in the designer's guide (pdf). I would like to point you there for further information.
I suppose you mean the "loop" as described by BO in universes. The description of loop is slightly misleading, cause it has nothing to do with a loop in terms of programming (i.e. do ... while ...)
You do not choose for a loop, but in creating a universe it is quite quickly possible that tables are joined in more than one way, thus creating a loop. If you then fire an SQL at the universe, the actual path is no longer defined, there is more than one way the query can be executed (and typically, there only one good way!)
Documentation on designer gives you 2 possible solutions:
1. Create contexts
2. Create aliases
With detect loops you can check whether you need to define contexts, this is like pre-defining the path a query on the respective tables will use (i.e. the joins between tables as chosen in the SQL)
In some cases it is better to create an alias on a table (for instance if it is a lookup table , used by more than one fact-table) , thus eliminating the loop.
If you apply a context, the user can be prompted when running a report to choose from several contexts.
All of this and much more is very well documented in the designer's guide (pdf). I would like to point you there for further information.
Hello Bachevenu,
I suppose you mean the "loop" as described by BO in universes. The description of loop is slightly misleading, cause it has nothing to do with a loop in terms of programming (i.e. do ... while ...)
You do not choose for a loop, but in creating a universe it is quite quickly possible that tables are joined in more than one way, thus creating a loop. If you then fire an SQL at the universe, the actual path is no longer defined, there is more than one way the query can be executed (and typically, there only one good way!)
Documentation on designer gives you 2 possible solutions:
1. Create contexts
2. Create aliases
With detect loops you can check whether you need to define contexts, this is like pre-defining the path a query on the respective tables will use (i.e. the joins between tables as chosen in the SQL)
In some cases it is better to create an alias on a table (for instance if it is a lookup table , used by more than one fact-table) , thus eliminating the loop.
If you apply a context, the user can be prompted when running a report to choose from several contexts.
All of this and much more is very well documented in the designer's guide (pdf). I would like to point you there for further information.
I suppose you mean the "loop" as described by BO in universes. The description of loop is slightly misleading, cause it has nothing to do with a loop in terms of programming (i.e. do ... while ...)
You do not choose for a loop, but in creating a universe it is quite quickly possible that tables are joined in more than one way, thus creating a loop. If you then fire an SQL at the universe, the actual path is no longer defined, there is more than one way the query can be executed (and typically, there only one good way!)
Documentation on designer gives you 2 possible solutions:
1. Create contexts
2. Create aliases
With detect loops you can check whether you need to define contexts, this is like pre-defining the path a query on the respective tables will use (i.e. the joins between tables as chosen in the SQL)
In some cases it is better to create an alias on a table (for instance if it is a lookup table , used by more than one fact-table) , thus eliminating the loop.
If you apply a context, the user can be prompted when running a report to choose from several contexts.
All of this and much more is very well documented in the designer's guide (pdf). I would like to point you there for further information.
- Status
Similar threads
- Locked
- Question
- Locked
- Question