Joining Type II Dimension Hierarchy directly to Fact versus through...

Using a dimension in multiple fact tables with different grain and support SCD

Hello users, i've a question about using a dimension in fact tables with different granularity and at the same time retain support for SCD. My scenario: I have one Dimension called Apartment. This Dimension cosists of the following related

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

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

Loading Fact Table with Type 2 Slowly Changing Dimension

I'm new to data warehousing .. sorry if this is a basic question. I have a type 2 slowly changing dimension already loaded and now I want to load a fact table. At least, I think it should be a fact table. A lot of the entities in the dimension table

Large Dimension table compared to fact table?

I may be misguided in my attempt to make a dimensional model here, but I will explain the scenario. We provide a value add service in the supply chain business...in this case by depicting a scorecard of the accuracy of vendors' product sizing

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

How to handle a Type I or II dimension with a snowflaked customer sub dimension (kimball book page 337, 338)

Hello, Within Ralph his new book he describes recommanded situations for snowflaking a dimension. His example is a large customer (visitor) dimension. (page 337, 338 and figure 10-6). I find the artical good, but there is missing one part of this

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

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

How fast can you type? (AWPM)

Well, here's my question. How fast can YOU type (Adjusted Words Per Minute, which means the CORRECT words per minute you type)? I personally type at a 60 AWPM, and a 65 WPM (WPM includes errors)

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

Joining Type II Dimension Hierarchy directly to Fact versus through a Dimension table