Universe Connections properties - best practice - Thoughts?

[former_member272336]

Hi,

We create relational connections to oracale database and tend to leva the defaults e.g keep one for 10 minutes etc.

Is there any best practice reagrading connection properties when settuing up connections

Thanks

[Former Member · Accepted solution]

Hello,

Best practice.

1. The performance of the universe is based on the way the structure is created.

2. Array fetch size – it is suggested this is set as large as possible. Although Business Objects allows it to be set to 999, it is always reset to an internal maximum of 500. This setting controls how many rows are passed back from the database through the middleware in a single fetch. Basically the higher the number, the less fetches, the less fetches, the faster the query results are passed back through the middleware to Business Objects. This only affects the fetch stage of a query execution, it does not affect how quickly the database takes to determine the first set of rows that it wishes to return. Think of a fetch as something similar to a single transaction between the middleware and the server its connecting to.

3.Keep the connection alive for X minutes – this avoids repeatedly opening and closing connections (as per ‘disconnect after each transaction’) and also avoids keeping connections open for excessively long periods (as per ‘keep the connective active during the whole session’). The amount for X is left to the developers discretion but it is suggested to be no more than 10 minutes.

4. Business Objects recommends you keep the default

connection life-time. The universe building process

slows significantly if the Connection Pool Mode is set

to disconnect after each transaction. Disconnecting after

each transaction also impacts key end-user workflows

such as working with hierarchical list of values.

Regards,

Laxminarayana

[former_member272336 · Accepted solution]

Hi Laxminarayana,

Thansk for this useful advice.

With regards the default connection life-time.  What is it and where is it set?

Thanks

[Former Member · Accepted solution]

Hello Philip,

What I meant was to set "Keep the connection Active" for 10 minutes. That was the default connection life-time.

Regards,

Laxminarayana

[former_member272336 · Accepted solution]

Hi Laxminarayana,

Thanks for update.

Thanks

[Former Member]

Hi Philip,

You can set Universe parameter "Keep the connection alive for X minutes" to achieve this. In my opnion for real time production scenario it is not recommended to set connection limit as 10min which is less because for few session/report query run more than X minutes. Also not recommended to restrict the query size limit. Array fetch size size is depend on the backend database and bandwidth availability. I hope this information help you to set the connection properties to optimum.

Regards,

Kamal.

[former_member272336]

Hi Kamal,

Thanks for advice.

Philip