We have recently started migrating more applications out of the 4GL to ODBC/JDBC and are seeing performance issues on the database.

Are here any best practices and tuning recommendations to enhance JDBC connection performance and keep it from impacting the other clients?

marc (AT) rohde-net (DOT) us wrote:

If you're putting a little skinny wire between your users and their
data, push the business logic UP the wire instead of trying to cram the
data down it.

Or to put it differently, write set-oriented code that does as much
processing on the server as possible.

Other than that, maybe show us some of the queries and we'll see what we
can do.

--
Roy

UK Actian User Association Conference 2012 will be on Tuesday June 19 2012.
Register now at https://www.regonline.co.uk/ukiua2012
The latest information is available from www.uk-iua.org.uk.

On Saturday, June 23, 2012 12:50:13 AM UTC+3, ma... (AT) rohde-net (DOT) us wrote:
Can you identify the exact bottleneck ? performance issues sounds too general.
Do the queries run slow? Are there lengthy locks?
Is there connection lag ? (maybe use JDBC connection pooling)
Is the JDBC driver tuned?
Was the 4GL code written in procedural fashion and tighten up to select loops? then as Roy pointed out,you may have to switch to set based logic instead of following a similar 'cursor based'/procedural logic in the new app too

Is it ODBC or JDBC? because the ODBC drivers are notorious for performing worse no matter the underlying dbms