Populating Bridge Tables Technics
Hi, I'm trying to figure out which are the best practises concerning the populating and maintaining bridge tables using ETL tools. I have a transaction fact tables, and each row of it involves 1 or more rows of Departement dimension table. I gues

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

A fact table surrounded by a lot of references tables
I am reviewing a design which is about to be implemented after build. There is a fact table with 17(!!) foreign keys. 14 of these keys are two-letter codes pointing to reference-tables (as we call them). A reference table consist of codes with

Confusion - star, snowflake, bridge table
Appreciate your expert comment on following: Entities: Quote, Trade, DIRequest, Order User, Customer, Trader, Sales or Marketer and Product - User is a user who is using the system or interfacing with the system. i.e. requesting quote or placing a

Junk Dimension Naming
What do you call your junk dimensions? Do you use "junk" in the dimension name? Junk implies garbage so I don't like using it. Most dimensions are easily named since they represent a single person, place, thing, concept, or event. Junk

Remedy for a Bridge Table?
Hi folks, I'm looking to get rid of my bridge table. (yes I know why whould I want to do that?) Reason being that I am using Mondrian and as far as I can tell bridge tables don't fit. My Situation: I have many facts and many Participants each

BRIDGE TABLES
Hi In my data warehouse I have the following two dimensions Customers and Accounts, a customer can have 1 or more accounts, both are SCD Type 2 dimensions. To show the relationship between the dimensions I am considering creating a bridge

"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

Same attribute in multiple dimensions or Create new dimension?
Hi all - I'm struggling with this concept. I have 2 dimensions: Customer and Products. Both share a common single attribute that I'll just call "Owner" for now. If a customer purchased a product, the owner would be the same for both. I

how many dimensions is too many
If I have a fact table with too many dimensions --- over 30, does that mean I've created dimensions when they could have been attributes to another dimension table or possibly that I am trying to capture too many business processes within one fact table.

Joining Type II Dimension Hierarchy directly to Fact versus through a Dimension table
Given I have 3 tables, Workforce Event Fact, Department Dimension (Type II SCD), and a Department Hierarchy (Type II SCD), and assuming the DEPTIDs in the Department Dimension table are reflected in a BASEDEPTID field in the Dept Dimension hierarchy table

Multivalue attributes
I am working on a model for use by the fund raising unit of our university. They want to be able to do some CRM type reporting on our alumni / donor data. In creating a constituent dimension I have found that there are a large number of attributes tha

What to do when the weighting factor of a bridge table no longer seems relevant?
I have a fact table that has healthcare claims data. Since a given claim can have multiple diagnoses, I'll use a bridge table that links a bridgekey from the fact table to the bridge table. The bridge table will also have a diagnosiskey that ultimately

Snowflake or Star Schema?
Hi, I am doing some dimensional modelling for a "not for profit" Fundraising Company They solicit Funds from the WEB, Direct Mail and Phone Solitications, etc and all Transactions are stamped with the FundID. The legacy system has all

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