Transaction Performance

With respect to transaction performance, make sure you have carefully considered the following items:

•Overall database tuning

•Application-specific database tuning

•Network tuning

Try to make your SQL statements as efficient as possible, because the Developer will not optimize everything for you.

Be aware of the fact that derived data can yield positive performance on the server, but may also have a negative effect on the client.

Test joined columns with the Optimize Joined Columns Fetch property set to Yes and to No, because the optimization does not always yield positive performance statistics.

Tuning of memory use and resident cache must be included in the benchmark data. The more memory is used for different applications, the less memory is left for the transaction itself.

Beware of locking. Only apply deferred constraints when necessary.

If you have a modem connection, it is worth testing with Transaction Mode set to Batch Manipulation. However, you must not only check the performance, but also whether the behavioral changes that this can cause are still acceptable to the users.

Transaction Mode is an application property which you can set using the Windows Designer. For more information on the Windows Designer, see the USoft Windows Designer Help.