Advertisement

06.19.2008 at 04:01PM PDT, ID: 23500807
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

8.6

OLAP  - Star Schema - How to?

Asked by michaelrobertfrench in OLAP

Consider 2 tables that I want to incorporate somehow into an OLAP solution.

Customers (Customer Name, Age, StoreLocation, CurrentBalance)
One Row for each Customer
John Doe, 35, Modesto, $0

Customer Invoice(Customer Name, Period, AmountPurchase, AmountPaid, PurchaseType)
One Row  for each period  the customer made purchase or payment.

John Doe,  May2004,    $95.00,        $0,  Camping Gear
John Doe, June2004,           $0, $95.00,  Payment
John Doe,  Sep2007,  $505.00,        $0,  Bicycle
John Doe,  Dec2007,           $0,    $505,  Payment

So I have a typical One to Many type relationship but I want to put this into an OLAP.  
Beside the dimensions like Period, PurchaseType: PurchaseType don't I want to take the above 2 tables and put them into a single fact table?

Customer Name, Age, StoreLocation, CurrentBalance, May2004Purchase, May2004PurchaseType ...

Could be a very wide flat table that becomes the fact table.  How do you model this kind of table.
If the customer has been doing business for many years I could run out of columns.



Start Free Trial
[+][-]06.20.2008 at 01:25AM PDT, ID: 21829245

View this solution now by starting your 7-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zone: OLAP
Sign Up Now!
Solution Provided By: srnar
Participating Experts: 1
Solution Grade: A
 
 
 
Loading Advertisement...
20081112-EE-VQP-42 - Hierarchy / EE_QW_2_20070628