Performance of setup tables.

[Former Member]

Hi Friends,

How do we improve the performace when creating the setup table? Pls provide me an example to better understand the scenario.

Thanks,

Pk

[Former Member]

Hello Pk,

This may help you...........

Setup tables are kind of interface between the extractor and application tables. LO extractor takes data from set up table while initalization and full upload and hitting the application table for selection is avoided. As these tables are required only for full and init load, you can delete the data after loading in order to avoid duplicate data. Setup tables are filled with data from application tables.The setup tables sit on top of the actual applcation tables(i.e the OLTP tables storing transaction records).During the Setup run, these setup tables are filled. NOrmally it's a good practice to delete the existing setup tables before executing the setup runs so as to avoid duplicate records for the same selections.

The init loads in BW pull data from the set up tables. The setup tables are only used in case of first init/full loads.

San.