Dimensions in 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

Snapshot Dimension & Fact tables

We are currently designing a logical multidimensional model from an OLTP tables.Dimension tables have monthly snapshot because some of or all the attributes might change on monthly basis.The same situation for the fact table has monthly snapshot. I kno

relating 2 existing dimensions combined to a fact table

given: * 1 existing sales fact table; > 1.500.000.000 records * 1 existing product dimension; >= 300.000 records * 1 existing store dimensions; >= 1.000 records required: * 3 new attributes, defined by the combination of a certain store an

SCD Type 2 dimension and fact table being the same table

I am designing a dimensional model for employee data in a data warehouse. Right now I only register the basic information about the employee, like job title, department, language, FTE, etc. I have chosen to use an SCD Type 2 dimension since I want to keep

Help in declaring grain and identifying dimensions

Requirements: 3 Reports ----------------------- Source Systems: 3 Project DBs 1st Report : Portfolio Summary Details The project monthly details report will display project information i.e. summary actual costs from the Vendor History file

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

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

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

MDX(or something else) for getting history based on last dimension characteristic for SCD.

Hi everyone, I am implementing a cube and I run into a problem with slowly changing dimensions(SCD type 2). I guess it might be resolved somehow with MDX or somehow else, maybe you guys can help me to resolve it. The problem: I have SCD, say Policy wit

Random Facts October

They grow up so fast! RF: The staff is organising a birthday party for the forum, but don't tell anyone!