On our main SQL server I have setup a database called DataWarehouse which is a location that through DTS all other databases dump relevant data for analysis purposes. The DTS packages are doing ETL into, specifically, tables in this DataWarehouse database.

Would it be better if in this DataWarehouse database I used views instead of tables to pull information from the tables I need? It seems like this is easier than creating DTS packages to jump a new or changed data to the data warehouse.

Our main analysis is really on of one DataBase which is our ERP system. So it's not like were dumping 5 different database into one location. It's only 1

Thanks for the hel

-mike

That will create an excesive work load over your transactional server.

Onother point, what will happen in one or two years when you cleanse your
tables looking for performance? Your views will also loose data.

The idea of a DWH is avoiding OLTP server overload with heavy analysis
queries and of course, maintaing your valuable data in the long term.

Hope it helps.

Michael

"Michael Morse" <mike.morse (AT) micromo (DOT) com> escribió en el mensaje
news:2890C6D4-4CD1-439F-BA5D-E4B99B7D5508 (AT) microsoft (DOT) com...
analysis purposes. The DTS packages are doing ETL into, specifically,
tables in this DataWarehouse database.
easier than creating DTS packages to jump a new or changed data to the data
warehouse.
only 1.

Butthat load will be onlu during cube processing, I suppose at night when
transactional users are out. I like this idea as long as the transactional
system has good enough tables structure.
JMHO
Szymon

"Michael Prendergast" <mikepre (AT) hotmail (DOT) com> wrote