How to design a one to many relationship

dianaantova at 21h15
11
May
2009
How to design a one to many relationship

I have a student quarterly registration fact table. Every student has academic programs (majors) associated with him/her and each student can have up to 5 of them. And each major can start and end at different times and has multiple parameters including graduation information. My fact table will have these dimensions:

Time, Quarter, student, registration parameters, student programs, majors, etc.

How do I model the

Read more
Reply
About
This topic belongs to the forum

  • Data Warehousing and Business Intelligence based on dimensional modeling and the Kimball Lifecycle.

  • Numbers of topics : 1858
  • Numbers of messages : 8714
  • Numbers of users : 3801
  • Numbers of points : 1672
Similar topics
Many to many relationship question
Hi all. I know the common standard practice for many to many relationships is to use a bridge table, and I've done that already in my model. But I've come across a situation where I'm thinking of using a group table related directly with the fact. Let'
Help with true one-to-many relationship
I have been fortunate (or unfortunate?) to only have encountered one to one dimension/fact relationships in my previous DW experience. However I am now looking at medical claim payments, and have a service line fact. It relates to several dimensions
EDW Design Decision
There is currently a difference of opinion on how the EDW should be structured for ad-hoc reporting. One camp suggests that the dimensional design can easily support both ad-hoc and analytical reporting. While the other suggests that the dimensional
many to many relationship between dimension level
I need help to design dimension model. Detail of Dimension are as following: Dimension : Student, School Fact : Grade 1. Class_Year 2. School 3. Area 4. City Analysis Requirement are to drill up /down by above given hierarchy there is : M:1
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
Forums from same category
See also
more_less
Informations

2 Replies For the topic :
"How to design a one to many relationship"

This topic has been viewed 1123 times.

Last message :
11/05/2009 at 21h15 by "dianaantova"