REF - Star vs. Snowflake Schemas / Star Transformation with a Bitmap Index
| Topic ID: 645 | |
| Created By: | 2005-NOV-10 17:33:35 [Vitaliy] |
| Updated By: | 2007-FEB-13 22:47:44 [Vitaliy] |
| Status: | Open |
| Severity: | Normal |
| Read Only: | No |
|
3016
2005-NOV-10 17:33:35
|
||||
|
REF - Star vs. Snowflake Schemas / Star Transformation with a Bitmap Index
STAR SCHEMAS
"A star schema optimizes performance by keeping queries simple and providing fast response time. All the information about each level is stored in one row. Oracle Corporation recommends that you choose a star schema unless you have a clear reason not to." REFERENCE: Star Schemas
SNOWFLAKE SCHEMAS
"Snowflake schemas normalize dimensions to eliminate redundancy. That is, the dimension data has been grouped into multiple tables instead of one large table. ... While this saves space, it increases the number of dimension tables and requires more foreign key joins. The result is more complex queries and reduced query performance." REFERENCE: Schema Modeling Techniques
OPTIMIZING STAR QUERIES
"To get the best possible performance for star queries, it is important to follow some basic guidelines: - A bitmap index should be built on each of the foreign key columns of the fact table or tables. - The initialization parameter STAR_TRANSFORMATION_ENABLED should be set to true. This enables an important optimizer feature for star-queries. It is set to false by default for backward-compatibility. - The cost-based optimizer should be used. This does not apply solely to star schemas: all data warehouses should always use the cost-based optimizer." REFERENCE: Optimizing Star Queries ------------------------- REFERENCE: Star Schema question on AskTom
[edited by: Vitaliy at 22:47 (CST) on Feb. 13, 2007]