![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi, I have a fundamental question to ask. I have to populate 7 new data marts (Fact tables and non-shared dimensions) from our enterprise datawarehouse (EDW). So I have to import data from EDW, calculate measures and retreive dimension ids. The fact tables will have many rows and will be updated monthly (monthly snapshot). I'm using DTS to Extract-Transfert-Load the data. Our EDW has several tables with high volume (up to 140 M of rows for the largest table, around 800 GB of data for the overall database). To reduce the complexity and enhance the overall performance, as it is recommended, I will break up complex data load and transformation processes into multiple steps that uses temporary tables. Currently, there is 2 datamarts in production (developped 2 years ago). These 2 datamarts use also DTS to ETL the tables, but they use flat files instead of temporary tables to store and process data in the intermediate steps. I would like to know if there is a "performance" best practice to use flat files instead of temporary tables? Does anybody has experimented both procedures??? Thanks |
#3
| |||
| |||
|
#4
| |||
| |||
|
|
Hello Alan, Thank you for your answer. As you have suggested, I would certainly use permanent tables instead of temporary tables in the intermediate steps. But, I would like to know if the use of flat files to manipulate data instead of tables in the intermediate steps could be an option to improve performance, reduce the process time? Thanks Eric. |
![]() |
| Thread Tools | |
| Display Modes | |
| |