Please explain in detail with example about
1.Confirmed Dimension.
2.Junk Dimension.
3.Degenerated Dimension.
4.Slowly changing Dimensions
Answers were Sorted based on User's Feedback
1.Confirmed Dimension-
The dimensions which is used more than one fact table is
called conformed dimensions.
Ex-Product Dimension related to Order fact, Sles fact,,,,.
2.Junk Dimension-
A "junk" dimension is a collection of random transactional
codes, flags and/or text attributes that are unrelated to
any particular dimension.
A good example would be a trade fact in a company that
brokers equity trades.
fact would contain several metrics (principal amount,net
amount, price per share, commission, margin amount, etc.)
and would be related to several dimensions such as account,
date, rep, office, exchange, etc.
3.Degenerated Dimension-
In a data warehouse, a degenerate dimension is a dimension
which is derived from the fact table and doesn't have its
own dimension table.
ex-line no in a Facttable,,,,
4.Slowly changing Dimensions-
A Slowly Changing Dimension (SCD)is a dimension that
changes over time.It may change immediately and it may also
change quite rapidly.
ex-nothing but Inserts,updates,,,,
Any corrections:-
Srinu.srinuvas@gmail.com
Is This Answer Correct ? | 29 Yes | 3 No |
Answer / jyoti
Confirmed Dimension: Dimensions which can be used in more
than one subject area.
Better example is : TIME DIMENSION
Junk Dimensions:Which contains Flags,random values comes
under Junk/Dirty dimensions.
Degenerate Dimension:These dimensions are stored in the
Fact table,but these are not Measures.
Slowly chnaging Dimensions:Dimensions which are chnaging
over time .These are Therr types
1) TYPE1: Will not maintain any history
2) Type 2: will maintain current information as well as
history.
3) Type3: will maintain Part history data
Is This Answer Correct ? | 19 Yes | 8 No |
Few more additions to the above answers.....
Confirmed dimension: Dimesion which can be 100 % sharable
with other star schemas. In other terms it is connected to
more than one one fact table .
Ex: time dimension
Junk dimesion: stores low cordinality values (repeated
values),flagged values.
Ex: details of gender information(male/female)
Degenerated Dimension:The attribute in the fact table
directly comes from the source table not from any
dimensions called degenerated dimensions. these are also
called neither a dimension nor a perfect fact.
Ex:attribute order_no, comes from source
Slowly changing Dimensions:Dimesions which are changing
over a period of time called slowly changing dimensions.
Ex:salary of employee.
Is This Answer Correct ? | 9 Yes | 1 No |
1.A dimension table which can be shared by multiple fact
tables is know as confirmed dimension.
2.A junk diemesion with type discriptive data boolean , flag
datatype can't be used to discribed the key performance
integrator are know as junk dimension for
exple:productdiscription,address,zipcode,phone number
if a table contains the values which are neither dimension nor
measure is called degenerate dimensions for
exple:invoice-id,empno
Is This Answer Correct ? | 2 Yes | 4 No |
To provide support for Mainframes source data,which files r used as a COBOL files
I have the input file as col1 col2 col3 3 2 1 7 6 8 I should get the output as col1 col2 col3 1 2 3 6 7 8 ....What is the logic to get this? Is there any transformation which sorts row wise ? If not how to sort the incoming records row wise?
what is meant by data driven.. in which scenario we use that..?
1:when we develop a project what are the performance issue will raise?? KPIT 2:if a table have INDEX and CONSTRAINT why it raise the performance issue bcoz when we drop the index and disable the constraint it performed better??KPIT 3:what are unix commands frequently used in informatica??
what happens if you try to create a shortcut to a non- shared folder?
how can i invoke pmcmd in command line prompt
if we are extracting 600000 records from a source table so how much volume of records frequently we load in warehouse. (Iknow its depend on client requirement) still i want to know how much volume of records store in warehouse.
what is the method of error handling when session is running?
in aggregator transformation we want to get middle record how to implement, source containg empno,name sal,deptno,address
Suppose we have two source qualifier transformations sq1 and sq2 connected to target tables tgt1 and tgt2 respectively. How do you ensure tgt2 is loaded after tgt1?
Consider two cases: (1) Power Center Server and Client on the same machine (2) Power Center Sever and Client on the different machines what is the basic difference in these two setups and which is recommended?
what are presession,postsession success and postsession failure commands ?