0

More

Next Blog

Create Blog

Sign In

Cognossimplified
Saturday, 16 February 2013

Cardinalities in Cognos framework

Hi Guys,

Follow ers

Join this site

w ith Google Friend Connect

Members (46) More

Below is note on cardinalities .I have taken the content from IBM cognos helpguide .You can find
the same in cognos framework userguide .Just noting down point for my reference .
taken from IBM
Already a member? Sign in

IBM helpguide Link

Cardinality in Generated Queries

IBM Cognos 8 supports both minimum-maximum cardinality and optional cardinality.
In 0:1, 0 is the minimum cardinality, 1 is the maximum cardinality.
In 1:n , 1 is the minimum cardinality, n is the maximum cardinality.
A relationship with cardinality specified as 1:1 to 1:n is commonly referred to
as 1 to n when focusing on the maximum cardinalities.

Blog Archive

2015 (1)
2014 (45)
2013 (77)
December (6)
November (8)

Note --- so 0:1 to 1:n is also read as 1 to n

October (2)
September (13)

A minimum cardinality of 0 indicates that the relationship is optional. You specify a

open in browser PRO version

Are you a developer? Try out the HTML to PDF API

August (9)

pdfcrowd.com

minimum cardinality of 0 if you want the query to retain the information on the other
side of the relationship in the absence of a match. For example, a relationship
between customer and actual sales may be specified as1:1 to 0:n. This indicates
that reports will show the requested customer information even though there may
not be any sales data present.

July (19)

Therefore a 1 to n relationship can also be specified as:

March (5)

June (2)
May (1)
April (2)

February (7)

0:1 to 0:n

Governors in framework manager

0:1 to 1:n

Cardinalities in Cognos framework

1:1 to 0:n

Related Links in drill down/drill up .or

drill thr...

1:1 to 1:n
Use the Relationship impact statement in the Relationship Definition dialog box
to help you understand cardinality. For example, Sales Staff (1:1) is joined to Orders
(0:n).

Scope in Framework
Shortcut and Alias shortcut explained
Exporting Cognos package
Prompts in Cognos
January (3)

It is important to ensure that the cardinality is correctly captured in the model

because it determines the detection of fact query subjects and it is used to avoid
double-counting factual data.

2012 (37)
2011 (36)

When generating queries, IBM Cognos 8 follows these basic rules to apply cardinality:
Cardinality is applied in the context of a query.
1 to n cardinality implies fact data on the n side and implies dimension data on
the 1 side.
A query subject may behave as a fact query subject or as a dimensional query
subject, depending on the relationships that are required to answer a particular
query.

Possible end labels are

0..1 (zero or one match)
1..1 (exactly one match)

About Me

Kapil
I have been working for last 6
years in Hyderabad India as
Business Intelligence developer.
I have worked on wide range of
reporting tools like
Cognos,Microstrategy, Logixml. Also i have
worked on Mutliple ETL tools
Datastage,Informatica, Pentaho. I am using
this blog as a place to note down my
experience with issues. Usually i forget thing
over time as most ppl do.So its good to keep
a online journal.
View my complete profile

0..n (zero or more matches)

open in browser PRO version

Are you a developer? Try out the HTML to PDF API

pdfcrowd.com

1..n (one or more matches)

The first part of the notation specifies the type of join for this relationship:
an inner join (1)
An inner join shows all matching rows from both objects.
an outer join (0)
An outer join shows everything from both objects, including the items that do
not match. An outer join can be qualified as full, left, or right. Left and right
outer joins take everything from the left or right side of the relationship
respectively and only what matches from the other side.
Example
Cardinalities are set according to reporting needs and are not necessarily
based on data .Consider below example .Which will require a full outer join.
Consider example of sold date and product .there might be dates when no
product were sold and there can be product which were never sold .so the
cardinality shoud be 0:n :0:n (Full outer join)
but in actual case we want to see only products that were sold so we have
1:1 to 1:n we can also model it to outer join 0:n to 1:n base on requirement
Recommend this on Google

Posted by Kapil at 18:35

Labels: cardinalities, cardinality, Cognos, Framew ork

No comments:
Post a Comment

open in browser PRO version

Are you a developer? Try out the HTML to PDF API

pdfcrowd.com

Enter your comment...

Comment as:

Publish

Select profile...

Preview

Post a Comment
Newer Post

Home

Older Post

Subscribe to: Post Comments (Atom)

Simple template. Powered by Blogger.

open in browser PRO version

Are you a developer? Try out the HTML to PDF API

pdfcrowd.com