I encourage you to design for the data warehouse now. This will give you a head start on data warehouse data model and the data warehousing environment & architecture. There will always be some level of operational reporting that will be well served out of the application. There will also be a mounting/evolving set of information analysis and reporting requirements that will best supported from the data warehouse environment. I encourage this parallel design approach because it will help you to avoid building in "reporting oriented" database designs and programming logic into your application. Many times I see applications with summary tables and rolling summary tables and a lot of cpu cycles being chewed up processing and reprocessing the transaction details to produce those summaries and them report on those summaries. These are data warehousing activities.
Of course, budgets will be a consideration that will impact your approach.
For More Information
- Dozens more answers to tough data warehousing questions from Mike Lampa are available here.
- The Best Data Warehousing and Business Intelligence Web Links: tips, tutorials, scripts, and more.
- Have an DW tip to offer your fellow administrators and developers? The best tips submitted will receive a cool prize. Submit your tip today!
- Ask your technical data warehousing questions -- or help out your peers by answering them -- in our live discussion forums.
- Ask the Experts yourself: Our SQL, database design, Oracle, SQL Server, DB2, metadata, object-oriented and data warehousing gurus are waiting to answer your toughest questions.
Dig Deeper on Oracle data warehousing
Related Q&A from Mike Lampa
When trying to design a data warehouse, we often try to model the database on the operational data model. Are there any guidelines in trying to ... Continue Reading
What is a surrogate key in a table? Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.