Junk Dimension Naming | BoxesAndLines

Textual fact or Junk dimension?

Hello, I have been following the forum for a while now and I must say that many doubts about dimensional modeling have gone thank to you all. However I am facing now the modeling of a cube and I am somewhat stuck on what is the best

"Shared Dimensions" ... Complicates Usage of Data Warehouse??

Question about 'Shared' dimensions. I have the following shared dimensions: Dim_Shared_Status & Dim_Shared_StatusType Dim_Shared_Status contains: [Id], [StatusTypeId], [Name] Dim_Shared_StatusType contains: [Id], [Name] Now

dimension model for many indicators field

I have 30+ fileds that has either 1 or 0 ( true or false)value in a fact table Patid -- -- --- PTInd_1 Ptind_2 Ptind_3........ PTind_30 -- etc 1

Rapidly Changing Dimension

Hello, I have a slowly changing dimension table with 105 attributes. About 85% of the attributes are type 1 and the remaining 15% are type 2. I have 4 fields that are type 2 that change a lot more frequently than the rest of the type 2 fields. On a

Tracking Type2 SCD when using a dimension outrigger

With an outrigger table, a narrow band of attributes, usually with significantly lower cardinality than the main dimension, is in essence snow flaked off of the main dimension. Great technique for data management and maintenance. To hide complexity from

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

Supplier Dimension to include Customers & Employees

We are in the process of finalising Dimensions /Facts to be used in Datawarehouse. Already finalised separate dimensions (eg Customer,Supplier,Employee) to handle requirements of Sales,Purchace and Human resourses. During designing Accounts Payable Fact

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

Overlapping Dates in a dimension

Hi, I am wondering if someone could advise me on how to deal with this design problem. I have a promotion dimension keyed to a sales fact table. Initially, we thought that only one promotion could be active at one time for a sale, but it is actually th

Linking or Merging Similar dimensions from Different Source Systems

We've got a situation with the DW we're building where we have 2 seperate systems that we are wanting to bring the data together for cross analysis 1) The first system is the main operational system ie a contact management application that records

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

DATE OR DATE KEYS IN FACT TABLES

I've read different opinions about the usage of dates in fact tables. If a date is NEVER used to filter and only reported, what is the purpose of adding it as a date key instead of a plain date type? Aren't we wasting the resources to get to the date