Making the most of SAP BODS

Business Objects and Data services had become an integral part for the success and profit of every enterprise. So does the SAP BODS professionals. Here are the tips and tricks that help the SAP BODS professionals to make their jobs simpler and faster. These tips and tricks are intended to make the most efficiency and optimal consumption of resources while using SAP BODS.

•          Increase monitor sample rate. Ex... To 50K in prod environment.

•          Exclude virus scan on data integrator job logs.

•          While executing the job for first time or when changes occur with re-run. Select the option COLLECT STATISTICS FOR OPTIMIZATION (this is not selected by default).

•          While executing the job second time onwards. Use collected stats.(this is selected by default)

•          Degree of parallelism (DOP) option for your data flow to a value greater than one, the thread count per transform will increase. For example, a DOP of 5 allows five concurrent threads for a Query transform. To run objects within data flows in parallel, use the following Data Integrator features:

Table partitioning

File multithreading

Degree of parallelism for data flows

•          Use the Run as a separate process option to split a data flow or use the Data Transfer transform to create two sub data flows to execute sequentially. Since each sub data flow is executed by a different Data Integrator al_engine process, the number of threads needed for each will be 50% less

•          If you are using the Degree of parallelism option in your data flow, reduce the number for this option in the data flow Properties window.

•          Design your data flow to run memory-consuming operations in separate sub data flows that each use a smaller amount of memory, and distribute the sub data flows over  different Job Servers to access memory on multiple machines.

•          Design your data flow to push down memory-consuming operations to the database.

•          Push-down memory-intensive operations to the database server so that less memory is used on the Job Server computer.

•          Use the power of the database server to execute SELECT operations (such as joins, Group By, and common functions such as decode and string functions). Often the database is optimized for these operations

•          You can also do a full push down from the source to the target, which means Data Integrator sends SQL INSERT INTO... SELECT statements to the target database.

•          Minimize the amount of data sent over the network. Fewer rows can be retrieved when the SQL statements include filters or aggregations.

•          Using the following Data Integrator features to improve throughput:

Using caches for faster access to data

Bulk loading to the target.

•          Always views the SQL that Data Integrator generates and adjust your design to maximize the SQL that is pushed down to improve performance.