Star Schema vs All in one table

daredevil at 11h52
11
Nov
2010
Star Schema vs All in one table

Hi,

I have a scenario where we have dimensional information and the facts in one table rather than a traditional break up into facts and dimensions. What could be the problem i could run into with having all information in one table. Thanks.
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
We hear a lot of BI implementations using star schema. (with few dims snowflaked sometimes ) Why not choose a flat table with all data put together instead of a star schema? (well , this question may seem strange, but please help me out here) Few
Hi, I am new to a financial company and I was asked to model two new sources of data in the existing mortgage data mart (not too sure if you could actually call it a datamart after seeing the design), basically I was asked to create detail information
Can anyone list the advantages and disadvantages of Star vs. Snowflake in your DW environement . And has anyone switched from one to another and why?
Hello, I have a very basic question. Can anyone please, explain the difference between a cube and a star schema? I studied about Star schema. When I implement it in Oracle Warehouse Builder 11g, I have to create a cube. Am I doing right? regards,
I'm designing a data mart for employee compensation. The measures will include things such as salary and various bonuses. Most of the data marts I've designed so far have fallen rather gracefully into a star schema. For this one, however, I have
Forums from same category
See also
more_less
Informations

10 Replies For the topic :
"Star Schema vs All in one table"

This topic has been viewed 1964 times.

Last message :
11/11/2010 at 11h52 by "daredevil"