using designer to build a basic universe

8/13/2019 Using Designer to Build a Basic Universe

1/17

Exercise 1: Creating Universe using quick design wizard for the following

schema in Data Mart of access database:

Faculty

FacultyId,FLname,FFname,Address,CountryId

Student

Sid,Sname

Student_AgeGroup

Agegroup LowerAge HigherAge

Skill

SkillID,SkillName,Fees

Faculty_Skill

FacultyId,SkillId

FeePaid

StudentID,SkillId,Paiddate,Fees,Tax

Also Create a procedure in oracle to populate below mentioned Time table:

DateDim

Dateinfo

Year

Qtr

Month

week


2/17

Create below mentioned dimensions / fact and measures in new Universe that

u create in this exercise

Student

Sid,Sname

Student_AgeGroup

Agegroup LowerAge HigherAge

Faculty

Fid , Fname

Skill


Faculty_Skill

FacultyId,SkillId

FeePaid

StudentID,SkillId,Paiddate,Fees(measure),Tax(measure)

Sample steps for creating universe are indicated below:


3/17

2.


4/17

3.


5/17

4.

5.


6/17

Exercise 2:

Add manually tables and create universe with classes and objects mentioned

above

Exercise 3:

Opening Universe file that has been created in above exercise

Exporting Universe file to CMS created in exercise 2 Importing from CMS Universe that is created in ex 2

Exercise 4:

Create below mentioned reports in Desktop based on setting equijoin ,

outerjoin and theta join in universe:

a) Faculty ,fname , address and the corresponding skills they can teach.b) List faculties with their corresponding skills and those who donot have

any skills also

c) List Students with their names and agegroup


7/17

Exercise 5:

Resolving Loops

Add below tables to same access db above

The tables and their columns are shown below:


8/17

You run a query to obtain the following information:

Names of customers

Customer's country of residence

Dates of each order

Destination country of the shipment

It will not be able to generate results shown below which is solved by aliasing


9/17

Solution:

Create an alias called destination

Exercise 6:

Chasm Trap

A chasm trap is a type of join path between three tables when two "many-to-one" joins converge on a

single table, and there is no context in place that separates the converging join paths.

Actual info:


10/17

Inflated data: without context

Club universe

View list mode

univ5

Exercise 7:

FanTrap

A fan trap is a type of join path between three tables when a "one-to-many" join links a table which is

in turn linked by another "one-to-many" join. The fanning out effect of "one-to-many" joins can cause

incorrect results to be returned when a query includes objects based on both tables.


11/17

Example: A fan trap inflates results

Using the schema above, an Interactive Analysis user runs the following query:

The following results are returned:

However, the end user adds the dimension Model ID to the query as follows:

The following report is created with the returned results:


12/17


13/17

Exercise 9:

multiple domain lookups

Example:

Country City

Ex 10:

Custom hierarchy

country:

cID

cName


14/17

State

Sid

Sname

cid

city

cid

cname

sid

Create below hierarchy from above classes:

Country_State_City

Cname

Sname

cname

Exercise 11:

Create following derived table

Table Name: DEPT_TOT_SAL

Columns:


15/17

DEPTNO,SUM_SAL ( this is sum of sal of each deptno)

Insert derived tables

Exercise 12

Short Cut Join

Which faculty teaches what skill without loop

Skill


Faculty

Fid , Fname,Skillid

FeePaid

StudentID,SkillId,Paiddate,Fees(measure),Tax(measure)

Exercise 13:


16/17

Creating LOVs

Display faculty based on fid selected thru LOVs

Get list from personal files

Display faculty based on fid selected thru LOVs

Hierarchy LOVs

Create Hierarchy LOV as follows

Year -qtr

Use the above lov for displaying students who have paid amount in a particular

qtr of a year

Exercise 14:

Create a Cross tab report as follows:

Qtr1 qtr2 qtr3

Salesmanname

King 100 400 500

Mike 200 600 700

Anthony 300 800 900


17/17

using designer to build a basic universe

Documents