WhereScape's Chuck Kelley has written a blog for BeyeNETWORK on the performance trade offs between joins and storage.
The question he asks is:
What is the best performing way to load a fact table that has 20 different dimensions?
As he sees it, there are 3 options:
- Create the table from a single FROM … WHERE clause
- Create a view that does the FROM … WHERE clause and join that to the input for the fact table
- Create the table with multiple staging steps joining
The full blog is available at http://www.b-eye-network.com/view/12675