Granularity - One Fact Table or Two

One Fact table having records at different granularity level

Hello, My question is just validation for an approach that we followed for one of our client requirements. Based on the requirement the FACT table should be constrcuted by the records from 2 Source table A and B. The structure of the table is as

Source for Accumulating Snapshot Fact table

I have a question about accumulating snapshots and I was hoping someone could shed some light on the subject. Does Kimball give any guidance anywhere (books, online, etc.) as to whether one should build the supporting transactional fact tables that

Two Grains for Time

I am having trouble with designing the date dimension for a financial data fact table. We have two different planning approaches. An annual plan, which consists of months, and a strategic plan, which consists of the next five years. The problem is that

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

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

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

Combination of SCD2, partial snowflake, Effective and end dates in fact table

We are creating dataware housing for multitanant based systems for HR module. Requirement ?Able to report on historical data for any given data time. Active employees headcount till given date. (as of that day) Onhire and termination based on perticula

Questionnaire for medical record entries

Good afternoon, I am currently working on a data warehouse in the health care sector and I currently facing this problem: The aim of this warehouse is to have an overview of a cancer therapy. So, I have created the following fact table

Bridge tables versus massive junk dimensions

I am designing a star schema to store information on hospital stays. This is my first real star schema and things are off to a good start. My fact table is hospital stays. I have a diagnosis dimension. There are multiple diagnoses per stay. Costs are

Bridge Table and Customer Hierarchy

Does anyone know of a good detailed reference that discusses populating and maintaining customer hierarchy type bridge tables? The only decent resource I've found is the "The Data Warehouse ETL Tool Kit", but it only briefly shows an example on

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