| Table Denormalization Study in PowerPivot |
| Written by Marco Russo |
| Friday, 05 February 2010 01:15 |
|
I recently talked about memory usage in PowerPivot and previously I wrote about difference modeling options using table normalization or not. Thus, I wondered whether table normalization is a good practice for performance and memory or not. The short answer is that yes, it might be better but not so much as you might suppose (and there are difference considerations about processing and query performance). Rule of thumb: a star schema is always a good thing! Have a good reading. - PowerPivot allows definition of relationships between tables loaded in a PowerPivot model. However, whenever these tables come from the same relational database, the same data could be loaded into a single table, by using data denormalization in the SQL query itself.
|
Author articles
- Using SSAS 2005/2008 as PowerPivot Data Source: Measures Are Imported as Text Columns
- Using SSAS 2005/2008 as PowerPivot Data Source: Direct MDX
- Using SSAS 2005/2008 as PowerPivot Data Source: Calculated Members
- Using SSAS 2005/2008 as PowerPivot Data Source: Query Designer
- Using SSAS 2005/2008 as PowerPivot Data Source: Calculated Members
Most Popular
- Step by step guide on installing PowerPivot for SharePoint on a single machine
- List of suggested datasets to test PowerPivot
- List of PowerPivot DAX functions with description
- How to install PowerPivot for Excel and list of know issues
- Microsoft Virtual Lab: PowerPivot for Excel 2010 Introduction
- List of PowerPivot DAX functions (short)
- PowerPivot's impact on BI pros?
- Recorded webcast - A Preview to PowerPivot Server Best Practices

