Q
Problem solve Get help with specific problems with your technologies, process and projects.

Design recommendations for FACT TABLE and DIMENSIONS

We are in the phase of warehouse designing. What are the recommendations and restrictions for FACT TABLE and DIMENSIONS?

We are in the phase of warehouse designing. What are the recommendations and restrictions for FACT TABLE and DIMENSIONS? What other things should be taken care of?

The choice of whether a table is a dimension or a fact are pretty clear. Dimensions are tables that contain attributes that describe an object. A fact is a table that collects quantitative information, such as sales. So I don't really see any restrictions.

If we think in terms of functionality there are always physical and data limits. These are where you will find limitations. When creating facts and dimensions you must consider the ultimate size of the object as well as access paths. You will generally add indexes to help you with both.

From a logical design perspective, there should be no restrictions. Build based on current and future requirements. You must make sure you build as much flexibility as possible into your design so that you can allow for future enhancements without having to rebuild your data.

This was last published in August 2005

Dig Deeper on Oracle data warehousing

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.

-ADS BY GOOGLE

SearchDataManagement

SearchBusinessAnalytics

SearchSAP

SearchSQLServer

TheServerSide.com

SearchDataCenter

SearchContentManagement

SearchHRSoftware

Close