Optimal MaxDB parameters for non SAP applications

[simon_matter]

Hello,

I'm still wondering how to achieve optimal parameters for MaxDB in non SAP environments.

I remember that in another thread Natalia kindly told me that - for example - the recommended setting for 'UseVectorIOSimulation' is now 'NEVER', which is not the default when installing MaxDB.

Looking the the 'SAP MaxDB Parameter Check File' I can see that it checks and also recommends this value. However, I always thought the parameter check file is mainly used for SAP environment otherwise the recommended default values could have been set in the MaxDB software itself.

So the question remains how to find out the best/recommended settings for MaxDB in non SAP environments. Did I miss something?

Thanks,

Simon

[lbreddemann]

Hi Simon,

the MaxDB development team always tries to make the "best" parameter settings default, so that the user don't have to spend too much time on tuning them.

The goal is to have a database that just runs after installation. In my opinion they have achieved that pretty well.

However, there are of course bugs in MaxDB (as there are in any other piece of code), that may lead to wrong result sets, slow performance or data loss. Some of those bugs occur when using code paths used with special features (e.g. join-implementations). Luckily the MaxDB developers are aware of the fact, that there may be errors in their code, so they started to create parameter switches for new features/functions/implementations. That way, the user can always switch back to the old working implementations in case anything goes wrong.

Thus, most of the parameter recommendations that are given for SAP environments are about avoiding bugs.

Therefore, you can safely just use the parameter check also for your NON-SAP MaxDB instances.

BTW: the way MaxDB is used by the SAP applications is not different from the way any other application uses it.

Best regards,

Lars

[lbreddemann]

Hi Simon,

the MaxDB development team always tries to make the "best" parameter settings default, so that the user don't have to spend too much time on tuning them.

The goal is to have a database that just runs after installation. In my opinion they have achieved that pretty well.

However, there are of course bugs in MaxDB (as there are in any other piece of code), that may lead to wrong result sets, slow performance or data loss. Some of those bugs occur when using code paths used with special features (e.g. join-implementations). Luckily the MaxDB developers are aware of the fact, that there may be errors in their code, so they started to create parameter switches for new features/functions/implementations. That way, the user can always switch back to the old working implementations in case anything goes wrong.

Thus, most of the parameter recommendations that are given for SAP environments are about avoiding bugs.

Therefore, you can safely just use the parameter check also for your NON-SAP MaxDB instances.

BTW: the way MaxDB is used by the SAP applications is not different from the way any other application uses it.

Best regards,

Lars

[simon_matter]

Hi Lars,

Thanks for your explanations. In short I understand that the defaults, which we are mostly using, is fine and we don't have to care too much.

I can confirm that MaxDB works very well with those settings, I just wanted to make sure I'm still on the right track - after using MaxDB(SapDB,AdabasD) for more than a decade

Thanks,

Simon