Snapshot Dimension & Fact tables

Updating Periodic Snapshot Fact Tables

What are the best practices for maintaining periodic snapshot fact tables if the atomic data that created them is modified? We have a couple periodic snapshot tables that capture new inventory and new revenue at the end of every month. Sometimes the

Subscription as an Accumulating Snapshot Fact or a Dimension?

I am designing a data mart for a subscription based service (my first data modelling effort). Each customer can have multiple accounts and each account can have multiple subscriptions. I have added a Sales Fact table and a Monthly Subscription Snaphot

Conformed Dimension for Transaction Fact and Accumulating Snapshot Fact Table

I'm working on a new warehouse application for reporting against our IT Project database. I want to create both a transaction fact table and an accumulating snapshot fact table. The project database (source) consists of multiple normalized tables to

Accumulating snapshot with SCD?

Is it common to update dimension keys within an accumulating snapshot fact table if it contains some slowly changing dimensions? Or is good practice to leave the keys alone and only use a more current key for new rows? My inclination is to leave the

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

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

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

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

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

Dimensional Model Vs Views as Structure for BOBJ Universe

I have a fairly complex data mart (multiple fact tables: 5 at the moment and several more coming; 4 shared dimensions across the 5 facts, 26 total dimensions and several bridge tables). I used standard best practices for building the Business Objects

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

Dimension loading sources

Hi all, It's about datawarehouse dimension loading : should i load dimension from a master data management referential or from the truth of my business application. In the first case, dimension will be cleaner than in the second case but it will not

Announcements and Sticky topics in seperate tables!

Yep, according to the topic /other-problems-f46/possible-t76511.htm it isn't possible to split global announcements and stickies in a seperate table. I'm suggesting for this to be possible! I hate it when the forums are so messed up! I'm sure the