Large Dimension table compared to fact table?

fact table as a dimension

Hi I'm presently modeling a data mart and I would like to use a fact table as a dimension for another fact table. Is it something doable and efficient or is there a better way to do that? if yes should i just create a surrogate key and link both

Monster dimension, joining fact tables

I am newbie to the DW. We have document processing OLTP system with the following tables Document table (partitioned table, approx. 1 billion rows) DocId -PK Title DocDate 10 other columns Users table UserId -PK UserName .. 3 other

Fact Table Indexing Strategy

Please explain the indexing strategy which is in use in your organisation for fact tables in your current database(oracle, sybase, db2) Specify volume as the indexing strategy may be based upon the volume of data. Is there a well laid out strategy

Large Fact Table and Maintaining Periodic Snapshot: Practice

I would like some opinions with my approach here. I am trying to replace an overkill lift and load ETL process that basically replicated the entire universe of dataset every period instead of doing just Delta Load. In this delta approach, I have a stage

NULL Values in Fact Table

In an Accumulating Snapshot that has multiple dates, where we are revisiting the fact rows as additional events occur, should the foreign keys to the date dimension for dates that have not yet occurred be set to NULL or should they point to a

Transactional detail fact table w/complimentary snapshot table. How do the two play together?

Take a detail daily banking transaction table with standard credit and debit level transactions. I want to build the accompanying snapshot that would present the higher level rollups of these lower transactions: There are about 250 daily transaction

Fact table with multiple date ?

Hi, I am modling a fact table for prisoners inscription in order to track historical changes. An admission is the hole stay comprise of one or many inscriptions usually separated by transferts between institutions. In the transactionnal system, it

Montly Snapshot views with transactional Fact table w/SCD2

I am a new at working with Dimensional Database design. I am struggling with something that probley is real easy to do, but just can't find documentation that will explain it. I want to create a monthly snapshot view of my transactional Fact table with

Audit Dimension Help

Hello all. I'm at the stage now where im building the audit dimension for my warehouse. I am having a little trouble figuring out a few things though. How do you aggregate the data from the error event fact table into the audit dimension? Some records

Sparse dimensions, how to handle?

I've purchased the book "The Microsoft Data Warehouse Toolkit" and have reviewed it in order to build out a data warehouse solution I am currently designing. I am stuck in a spot that I don't seem to find any examples of , or am not abl

fact table as a dimension

Hi I'm presently modeling a data mart and I would like to use a fact table as a dimension for another fact table. Is it something doable and efficient or is there a better way to do that? if yes should i just create a surrogate key and link both

Regarding Factless Fact Tables

Some time ago I was asked to build the BI platform for a road safety organization. The warehouse was built of three primary fact tables, each with a collection of associated dimensions. I am now trying to branch out into ETL and Warehouse design, and from

100 reasons why Madeleine was not abducted

http://blogs.news.sky.com/discussions/show.html?plckForumPage=ForumDiscussion&plckDiscussionId=Cat:746f9309-1bb1-4b07-ad11-647f5ba16800Forum:4237bf3e-0948-444d-a452-46289a2fd1f7Discussion:53085ce6-d0e9-4517-9607-a2eb2b4b9b84 class=Discussion_PostTi