GeekInterview.com
  I am new, Sign me up!
 
GeekInterview.com  >  Interview Questions  >  Data Warehousing  >  Business Objects
Go To First  |  Previous Question  |  Next Question 
 Business Objects  |  Question 226 of 253    Print  
Business Objects cardinalities
Why do we need cardinalities with joins, when we are able to get the data with joins only?


  
Total Answers and Comments: 5 Last Update: April 21, 2009     Asked by: zeenat14 
  
 Sponsored Links

 
 Best Rated Answer
Submitted by: garycronin
 
Cardinality expresses the minimum and maximum number of instances of an entity B that can be associated with an instance of an entity A. The minimum and the maximum number of instances can be equal to 0, 1, or N. Because a join represents a bidirectional relationship, it must always have two cardinalities. If you selected the Detect cardinalities in joins options in the Database tab of the Options dialog box, Designer detects and retrieves the cardinalities of the joins. If you do not use this option, you can still retrieve the cardinalities for one or all joins in the universe. There are two main methods for detecting or editing cardinalities: the Detect Cardinalities command the Edit Join dialog box

Above answer was rated as good by the following members:
mindblue
May 08, 2008 11:24:13   #1  
skcmadduri Member Since: September 2007   Contribution: 2    

RE: Business Objects cardinalities
You need to setup cardinalities inorder to find loops and traps (fan trap & chasm trap)
 
Is this answer useful? Yes | No
May 28, 2008 09:04:31   #2  
garycronin Member Since: May 2008   Contribution: 3    

RE: Business Objects cardinalities
Moreover to effectivily use data on tables that are joined you must state the cardinality. Bobj can get it wrong sometimes so I'd advise you to set them up manually.

 
Is this answer useful? Yes | No
May 28, 2008 09:58:02   #3  
garycronin Member Since: May 2008   Contribution: 3    

RE: Business Objects cardinalities
Cardinality expresses the minimum and maximum number of instances of an entity B that can be associated with an instance of an entity A. The minimum and the maximum number of instances can be equal to 0 1 or N. Because a join represents a bidirectional relationship it must always have two cardinalities. If you selected the Detect cardinalities in joins options in the Database tab of the Options dialog box Designer detects and retrieves the cardinalities of the joins. If you do not use this option you can still retrieve the cardinalities for one or all joins in the universe. There are two main methods for detecting or editing cardinalities: the Detect Cardinalities command the Edit Join dialog box
 
Is this answer useful? Yes | NoAnswer is useful 1   Answer is not useful 0Overall Rating: +1    
April 13, 2009 18:58:19   #4  
Rajnish_kaushal Member Since: April 2009   Contribution: 10    

RE: Business Objects cardinalities

Main use of Cardinalities is to detect loops as said by one of member.

It is always advisable to manually assign cardinalities. Browse the database first figure out cardinalities and then apply the same manually. BOBJ can sometime take lot of time detect cardinalities as it traverse through individual record to figure out cardinality.

Regards


Rajnish Kaushal


 
Is this answer useful? Yes | No
April 19, 2009 14:50:12   #5  
ASHOK1324 Member Since: April 2009   Contribution: 36    

RE: Business Objects cardinalities

Cardinality describes a join between 2 tables by stating how many rows of one
table will match with rows of another table. It is very important to detect join
problems and to create the contexts to correct the limitations of a target
table.


BO designer can automatically detect and set cardinalities for each join.
But we manually check the cardinalities based on the nature of keys that are
joined.


Drag the column of first table to the corresponding column of second table or
simply go to Insert->Join to create a join between 2 tables.


You can manually change the cardinality from n-n [many to many] or 1-n or n-1
or 1-1 and Click on "Detect". In BO It is always best to use 1-n cardinality
for fast data retrieval. Always delete the unnecessary joins which have n-n
cardinality as these joins create loops.


 
Is this answer useful? Yes | No


 
Go To Top


 Sponsored Links

 
About Us -  Privacy Policy -  Terms and Conditions -  Contact -  Ask Question -  Propose Category -  Site Updates 

Copyright © 2005 - 2009 GeekInterview.com. All Rights Reserved

Page copy protected against web site content infringement by Copyscape