On Thu, Jan 24, 2013 at 7:43 AM, Prashanth Ranjalkar <prashant.ranjalkar@xxxxxxxxx> wrote:
be no DML operations executing on DWH DB which is mainly used for analyzing the data and getting the reports for making business decisions. After every data load process, statistices should be updated in order to gain the performance therefore it's best practice to add analyze command for the respective tables in ETL script itself. If auto vacuum is enabled on tables which participate in ETL process, autovacuum kicks off frequently when its threshold values met and keep running affecting data load process.If we disable autovacuum on table level (NOT at cluster level) auto vacuum never kicks off during ETL process and ETL job get finished quickly with analyze operation completed as well.
Hello,
Yes I know, but for this particular case we won't use a daily recalcuation, or a daily incremental load.
We want to do an incremental load up to 6times / day. 9or more, if possible, the ultimate goal would be to have all pre calculated data almost live in the dwh from the oltp systems)
Yes I know, but for this particular case we won't use a daily recalcuation, or a daily incremental load.
We want to do an incremental load up to 6times / day. 9or more, if possible, the ultimate goal would be to have all pre calculated data almost live in the dwh from the oltp systems)
So it needs some more tweaking and tuning than the average dwh. Because we are handling both very complex queries and star schemes, and still a high insert / update load. pretty much all the time.
But that's where the challenge is, I guess.
cheers,
cheers,
Bert
--
Bert Desmet
0477/305361
