Multiple Client Applications
Sometimes, two or more client/server applications may use the same database engine. You will need to configure the database engine differently depending on whether the applications are used at the same time.
If your vendors supply configuration guidelines for engine configuration parameters, you will need to adjust your configuration based on these guidelines.
If the applications run concurrently (that is, if two or more applications are using the database server at the same time) ...
You should configure the engine by adding together all the recommended values for each parameter. For example, if one application vendor suggests Performance Tuning | Number of Input/Output Threads should be set to 4, and another application vendor suggests this parameter should be set to 8, then you should set it to 12.
If the default value is higher than the sum of the recommended settings, then do not change the default value.
Do not add up the recommended values for any buffer size settings, or log file size settings. Use the largest recommended setting. Again, do not change the default if it is larger than any vendor recommendation.
If the applications do not run concurrently (that is, if only one application is running at any given point in time) ...
You should configure the server by using the largest recommended value for each parameter. For example, if one application vendor suggests Performance Tuning | Number of Input/Output Threads should be set to 4, and another application vendor suggests this parameter should be set to 8, then you should set it to 8.
If the default value is higher than the largest recommended setting, then do not change the default value.
Settings Affected by Multiple Applications
Most engine settings are not affected when you are running multiple applications. This section explains the settings that may need to be adjusted for multiple applications.
Compatibility | Create File Version
Some applications may require that new files be created with version 7.x file format, while other applications may require version 9.x file format (the default).
These applications can run concurrently only if new files are not created during runtime. There is no way to toggle the setting back and forth for each application, unless you wish to do it by hand or write a program to do so using the Distributed Tuning Objects.
If the applications do not create new files during runtime, then this setting is not relevant for multiple applications.
Data Integrity | Transaction Durability
Some applications may require durable transactions, while others may not. If you have two application vendors recommending different values for this parameter, then you should set it to On. Generally, having transaction durability turned on does not affect applications that do not use transactions, but may slow performance.