Jason Wharton wrote:

>>

There is a tradeoff. I say keep prepared those queries that are used on a
rather frequent basis. If they are only used infrequently or in a process
that isn't performance sensitive it would make sense to not keep them
prepared.
Also, since IBO does nothing to automatically Unprepare statements it would
be a good idea if ever there are things you do that you know are done for a
while to include code to explicitly unprepare the datasets and/or
statements.
<<

Different sets of statements are used depending on input. But I've seen
that some can be made more general, thereby reducing the necessary
cursor/query count somewhat.
I think I will go for 'all queries prepared', unless something unfortunate
turns up.

>>

It would be very interesting if you did some benchmarks and comparisons on
this.
<<

I will do this, I just have to start some testing of a new server that was
not cooperative. The correct driver for the RAID system was not installed
so there were crashes and blue screens galore, but after having people
scrathcing their heads for a couple of days I think we should soon be in
business.


Regards,
Aage J.