Interested to Buy Any Domain ? << Click Here >> for more details...
what is a junk dimension ?
- 14 Answers
- 62959 Views
- Atos Origin, Cognizant, HS, NIIT, TCS, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / vijay
A "junk" dimension is a collection of random transactional
codes, flags and/or text attributes that are unrelated to
any particular dimension.
The junk dimension is simply a structure that provides a
convenient place to store the junk attributes. A good
example would be a trade fact in a company that brokers
equity trades.
The 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. This fact would
also contain several codes and flags that were related to
the transaction rather than any of the dimensions ... such
as origin code (that indicates whether the trade was
initiated with a phone call or via the Web), a reinvest
flag (that indicates whether or not this trade as was the
result of the reinvestment of a dividend payout) and a
comment field for storing special instructions from the
customer.
These three attributes would normally be
removed from the fact table and stored in a junk
dimension ... perhaps called the trade dimension. In this
way, the number of indexes on the fact table would be
reduced, and performance (not to mention ease of use) would
be enhanced. Hope this helps.
| Is This Answer Correct ? | 57 Yes | 0 No |
Answer / aparna
A junk dimension is a convenient grouping of flags and
indicators. It's helpful, but not absolutely
required, if there's a positive correlation among the
values. The benefits of a junk dimension
include: ? Provide a recognizable, user-intuitive location
for related codes, indicators and their
descriptors in a dimensional framework.
? Clean up a cluttered design that already has too many
dimensions. There might be five
or more indicators that could be collapsed into a single 4-
byte integer surrogate key in
the fact table.
? Provide a smaller, quicker point of entry for queries
compared to performance from
constraining directly on these attributes in the fact
table. If your database supports bitmapped
indices, this potential benefit may be irrelevant, although
the others are still
valid.
| Is This Answer Correct ? | 20 Yes | 3 No |
Answer / srinu
junk dim is convient for group of flags and attributes to
get them out of a fact table inti useful dimension framework
| Is This Answer Correct ? | 15 Yes | 5 No |
Answer / pullareddy palle
junk dimensions are the dimensions which can not participate
in mapping data flow(not useful). like boolean, flags
| Is This Answer Correct ? | 7 Yes | 0 No |
Answer / arpita
A dimension which cannot be used to indicate the key
performance indicators is known as junk dimension.....
eg: Address,Phone number,Faxno,Description......etc...
| Is This Answer Correct ? | 7 Yes | 3 No |
Answer / mohan
junk dimention is a dimention table which holds only flags
or status where dimension field values are like True/False,
open/Close,complete/incomplete/inprogress, etc.
| Is This Answer Correct ? | 4 Yes | 0 No |
Answer / ramesh
what is junk dimension? Give an example
When developing a dimensional model, we often encounter miscellaneous flags and indicators. These flags do not logically belong to the core dimension tables.
A junk dimension is grouping of low cardinality flags and indicators. This junk dimension helps in avoiding cluttered design of data warehouse. Provides an easy way to access the dimensions from a single point of entry and improves the performance of sql queries.
Example: For example, assume that there are two dimension tables (gender and marital status). The data of these two tables are shown below:
Code:
Table: Gender
Id Gender_status
----------------
1 Male
2 Female
Table: Marital Status
Id Marital_Status
----------------
1 Single
2 Married
Here both the dimensions have low cardinality flags. This will cause maintenance of two tables and decrease performance of sql queries.
We can combine these two dimensions into a single table by cross joining and can maintain a single dimension table. The result of cross join is shown below:
Code:
id gender mrg_status
--------------------
1 Male Single
2 Male Married
3 Female Single
4 Female Married
This new dimension table is called a junk dimension. This will improve the manageability and improves the sql queries performance.
| Is This Answer Correct ? | 4 Yes | 0 No |
Answer / vamshi
In data warehouse design, frequently we run into a situation where there are yes/no indicator fields in the source system. However, if u keep all those indicator fields in the fact table, not only do we need to build many small dimension tables, but the amount of information stored in the fact table also increases tremendously,
Junk dimension is the way to solve this problem. In a junk dimension, we combine these indicator fields into a single dimension. This way, we'll only need to build a single dimension table, and the number of fields in the fact table, as well as the size of the fact table, can be decreased
The content in the junk dimension table is the combination of all possible values of the individual indicator fields
| Is This Answer Correct ? | 1 Yes | 0 No |
Answer / prakash m
A convenient grouping of random flags and attributes to get
them out of the fact table
Retain only useful fields
Remove fields that make no sense at all
Remove fields that are inconsistently filled
Remove fields that are of operational interest only
Design similar to demographics; maximum unique
combinations, assign integer key, plug into fact
Create new combination (insert new dimension record) at ETL
run-time
E.g. Yes/No Flags in old retail transaction data
| Is This Answer Correct ? | 2 Yes | 2 No |
What is Code Page Compatibility?
Why we need XMLs?
what is the size of your data warehousing?
How to display First letter of Names in Caps?
what are the different types of transformation available in informatica. And what are the mostly used ones among them?
Hi, In a mapping I have 3 targets and one fixed width file as source. Total 193 records are there . I connected one port in aggregator to all 3 targets. The same value need to be load into these 3 targets . It is loaded like that only but in different order. Why? The order of insertion should be same know for all 3 targets ? Then why the order is changed ? Any one please help me. Advance thanks.
How do we come to know the Source data/file is ready/Updated in the source location, when the session is scheduled for @12:00AM and ready to run its job ? or Can we schedule the session, when the source is updated in source location without any time constraint?
How do you use reject loader.
Had any one faced informatica(ETL/Developer), Datawarehouseing interview in UK. Than plz help me (i have any exprience of 3yrs informatica,datawarehousing,oracle,teradata) 1.hw the procedure will b here 2. wht type of question's they will b asking. 3.In which area they concertate more. since this is the first time im facing interview in UK. plz help ASAP.it will b a great help for me thanks to All in Advance
How will you combine 3 different sources with a single source?
What are the main issues while working with flat files as source and as targets ?
I am using Informatica 7.1.1. and i used emails task for getting emails but not able to get emails is there any settings in Informatica installation level?
Teradata 
