The pros of a data warehouse include the fact that the database is tuned specifically for the retrieval of historical data, slicing and dicing based on date ranges, part numbers or geographical regions, etc. It's tuned specifically for these queries so they better run fast! It's possible that your transactional database doesn't even have the historical data required to generate the reports you require.
The cons may be the potential size. These databases can be extremely large, which may require a significant hardware investment. Also, if your current expertise is more geared towards transactional systems, you'll either have to invest in data warehouse training or bring in external resources.
I'd recommend that you look into books by Ralph Kimball. He is the modern day guru and has some great offerings such as The Data Warehouse Toolkit: The Complete Guide to Dimensional Modeling (Second Edition), The Data Warehouse Lifecycle Toolkit : Expert Methods for Designing, Developing and Deploying Data Warehouses, and The Microsoft Data Warehouse Toolkit : With SQL Server 2005 and the Microsoft Business Intelligence Toolset.
Dig Deeper on SQL Server Data Warehousing
Related Q&A from Joe Toscano
Is there a query to search text in a SQL Server DTS package? SQL Server expert Joe Toscano explains which database objects can be viewed. Continue Reading
Migrate DTS packages to SQL Server Integration Services with Migration Wizard and deploy SSIS packages in SQL 2005. Learn how to access DTS Designer ... Continue Reading
Getting an error when importing data from an Excel spreadsheet to SSIS in SQL Server 2005? Try lining up data types in Excel and SSIS so they match. 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.