DSO Secondary Indexes on Active Tables created Directly in the Database

[Former Member]

Hi All,

In the wake of the performance issues with few of our BO reports ( based on Bex Queries) in production system, we have identified the need in adding few more secondary indexes (in addition to existing ones) on the underlying DSOs.

However, these secondary indexes have been directly created/added to the DSO Active tables in the Database( ) by our DBA team.

There was a significant improvement in the BO reports and all performance issues have been sorted out. We knew this is just a temporary fix and eventually, these indexes must be created in the DSOs and transported all the way to prod.

Now the concerns are,

1. If the additional indexes must be deleted by DB Admin before transporting the DSOs.
2. Or will the transport simply overwrite all the DB indexes in prod and replace them with the  indexes transported as part of the DSO.
3. Will there be any conflict or transport failure in the prod env( as the transport attempts to create the indexes in the back end table and finds the same index already existing on the same table).
4. Is there a standard way to deal this situation or is it as simple as transporting these DSOs by adding required new indexes?

Note: Our DBA team is speculating about deleting the indexes ( they are afraid as the deletion at table level may lead to inconsistencies to the entire DB           or at least to those specific Active Tables)

Please let me know your thoughts.

BW Version : 7.0

Data base    : DB6

Regards,

Sudheer

[sander_vanwilligen]

Hi Sudheer,

As of BW 7.0 it is according to me possible to define a secondary index in DSO modeling. To avoid any risk, I suggest to delete the manually created secondary index prior to the import of the transport request. If you have a proper "go live" timing, it should have a minimum impact on reporting performance (only a limited time of let's says minutes where no secondary index exists).

Best regards,

Sander

[former_member197660]

Hi Sudheer

As I know you cannot transport indexes of DSO tables, thus you have to create them explicitly in respective systems.

In our system we create them in all the system likewise to sync the objects across the systems.

I feel transporting a DSO could lead to complex situation as you have to take in account about the version of DSO's, activation of transformations etc.

Regards

Ashish

[former_member186053]

Hi Sudheer,

When you transport your DSO from Dev to Prod, secondary index will automatically moves to production along with your DSO. Or you can create index directly in Prod system itself.

Please go through the below thread which would clear your doubts.

Thanks,

Vengal.