Most efficient / least impact on database side -- Statement/PrepedStatement

Question

I have an application that will have a fully prepared sql string (i.e. no variable data). Although the sql string will frequently update the same table the data in the sql string will vary (making the sql string itself unique each time).
My application will run on a box that is separate from the box running the database. In what way can I reduce parsing on the database? It seems there are 2 roads to go down:
Road A:
- connection.getStatement
- statement.executeUpdate(sql string)
Road B:
- connection.prepareStatement(sql string)
- statement.execute( )

Answer 1

user552770,
Are you aware of what constitutes a different SQL string to the Oracle parser?
You can find a wealth of information on it from the Oracle documentation, the Ask Tom Web site and countless other books and Internet sites.
So are you sure your SQL is "different" in terms of the Oracle parser, or not?
Are you aware of statement caching and connection caching that are supported by the Oracle 10g database and JDBC driver? It may help improve performance in your situation.
In my experience, the biggest bottleneck is network traffic. I have found that it's much quicker to run the JDBC code on the same machine as the Oracle server and then serialize and transfer the results to the remote client. Of-course, you may get different results to me. I suggest you experiment and see what's best for you. I'm just trying to make you aware of the possible options.
Good Luck,
Avi.