GeekInterview.com
   Home |  Tech FAQ  |   Interview Questions |  Placement Papers |  Tech Articles |  Learn |  Freelance Projects |  Online Testing |  Geeks Talk |  Job Postings |  Knowledge Base | Site Search |  Add/Ask Question

GeekInterview.com  >  Interview Questions  >  Data Warehousing  >  Basics
Go To First  |  Previous Question  |  Next Question 
 Basics  |  Question 96 of 111    Print  
What are late arriving Facts and late arriving dim ? How does it impacts DW?

  
Total Answers and Comments: 1 Last Update: August 15, 2007     Asked by: Navin 
  
 Sponsored Links

 
 Best Rated Answer

No best answer available. Please pick the good answer available or submit your answer.
August 14, 2007 03:44:41   #1  
Are Ramakrishna Rao        

RE: What are late arriving Facts and late arriving dim...

Late arriving Fact table:

        This is rarely happens in practice.

For example there was a credit card of HDFC transaction happened on 25th Mar 2005, but this record we received on 14th Aug 2007. During this period there is a possibility of change in dimensional data.

There are two table one is transaction fact table and customer dimensional table

Transactional fact table is having two time stamps 1. Transaction date 2. Load date

Customer dimensional table is having two time stamps 1. Enter date (when customer provided the details) 2. Load date

In case of late arrive fact records we have get the proper key from the dimensional tables as these tables are maintaining the history.

In above scenario we have to extract the right key by using transaction date <= enter date from customer dimension table for the particular customer.

Late arriving Dimension table:
   This is very general practice in consumer finance projects

Some times we will get the transactional data without dimensional date. In this practice we will follow two methods.

1. Create one dummy record in dimensional table and join with fact table. Once we receive this data the dummy record in the Dim table will be updated using type SCD1
2. Place the transactional data in staging table till we receive the dim records. Re keying processed will be used to get the key from dim table

Re keying process: Generally in ETL process first we will load dim records and then go for facts. At the time of loading fact records keying will be done with dim tables. The unkeyed records will be kept in staging table and remaining data will be stored in target table. Next day at the time of keying process the unkeyed data will also used for keying is called as re-keying. Re-keying process will be continued till we get the key from dimensional tables

 
Is this answer useful? Yes | No

 Related Questions

Answer posted by Chintan on 2005-05-22 18:34:55: A relational database schema organized around a central table (fact table) joined to a few smaller tables (dimension tables) using foreign key references. 
Latest Answer : A data warehouse design that enhances the performance of multidimensional queries on traditional relational databases. One fact table is surrounded by a series of related tables. Data is joined from one of the points to the center, providing a so-called ...

Latest Answer : Non additive facts are the facts that do not participate in arithmetic caliculations. for example in stock fact table there will be opening and closing balances along with qty sold and amt etc. but opening and closing balances were never used in arithmetic ...

What are Semi-additive and factless facts and in which scenario will you use such kinds of fact tables

Explain the flow of data starting with OLTP to OLAP including staging ,summary tables,Facts and dimensions.
Read Answers (6) | Asked by : madhuom

Latest Answer : Late arriving Fact table:        This is rarely happens in practice. For example there was a credit card of HDFC transaction happened on 25th Mar 2005, but this record we received on 14th Aug 2007. During this period there is a possibility of change ...
Read Answers (1) | Asked by : Navin


 Sponsored Links

 
Related Articles

Breaking up XML into Relational Data

Breaking up XML into Relational Data While the preceding example shows how to construct an XML representation over relational data the example in this section illustrates how you can shred XML data back into relational data This reverse operation can be useful if your application works with relation
 

Querying Data with Oracle XQuery

Querying Data with Oracle XQuery Starting with Oracle Database 10g Release 2 you can take advantage of a full featured native XQuery engine integrated with the database With Oracle XQuery you can accomplish various tasks involved in developing PHP Oracle XML applications operating on any kind of dat
 

Retrieving XML Data

Retrieving XML DataTo retrieve XML data from an XMLType table you can use a SELECT SQL statement just as you would if you had to query a relational table For example to select the employee with the id set to 100 from the employees XMLType table discussed in the preceding section you might issue the
 

Using XMLType for Handling XML Data in the Database

Using XMLType for Handling XML Data in the Database Being an object type XMLType can not only be used to store XML data in the database but also to operate on that data via its built in methods Regardless of the storage model you choose XMLType provides a set of XML specific methods to operate on XM
 

Using Oracle Database for Storing, Modifying, and Retrieving XML Data

Using Oracle Database for Storing Modifying and Retrieving XML Data With Oracle XML DB you have various XML storage and XML processing options allowing you to achieve the required level of performance and scalability One of the most interesting things about Oracle XML DB is that it allows you to per
 

ODP.NET - Techniques to Improve Performance while Retrieving Data

ODP NET Techniques to Improve Performance while Retrieving Data Performance tuning is a great subject in Oracle Volumes of books would not be enough to cover every aspect of performance tuning in Oracle However in this section we will only discuss the fundamental performance techniques while working
 

ODP.NET - Populating a Dataset with a Single Data Table

ODP NET Populating a Dataset with a Single Data Table A dataset is simply a group of data tables These data tables can be identified with their own unique names within a dataset You can also add relations between data tables available in a dataset mosgoogle The following code gives you the details o
 

ODP.NET - Retrieving Typed Data

ODP NET Retrieving Typed Data While retrieving values from OracleDataReader we can extract information available in individual columns of a particular row either by using column ordinal position values or column names mosgoogle Retrieving Typed Data Using Ordinals ODP NET provides data specific enum
 

ODP.NET - Retrieving Data Using OracleDataReader

ODP NET Retrieving Data Using OracleDataReader OracleDataReader is simply a read only and forward only result set It works only if the database connection is open and it makes sure that the connection is open while you are retrieving data As the data that it retrieves is read only it is a bit faster
 

ODP.NET - Fundamental ODP.NET Classes to Retrieve Data

ODP NET Fundamental ODP NET Classes to Retrieve Data To retrieve data from an Oracle database using ODP NET we need to work with a few of the ODP NET classes At this point we will discuss the most fundamental classes available in ODP NET for retrieving data mosgoogle The following is the list of fun
 





About Us  |   Privacy Policy  |   Terms and Conditions  |   Contact  |   Site Map  |   Add Question  |   Propose Category  |   RSS Feeds  |   Articles Sitemap  |   Site Updates  |   Add Resource

Copyright © 2005 - 2008 GeekInterview.com. All Rights Reserved
Page copy protected against web site content infringement by Copyscape