Hello Joaquin,

j> I have seen in some documents that long running transactions may
j> create performance problems and high VM usage. The statistics of my
j> dbs seems ok (small diference between oldest tr and oldest active).
j> However in some parts of our UI we show a grid showing data and the
j> transaction used is active for the time that window is open. I have
j> seen that IB 7.1 has an option for
j> long-running-read-only-transactions
j> that do not impact on performance. Is this available in Firebird 1.5 ?
j> What parameters should be used ? (I use FIB and Firebird 1.5...).

With FIB you specify two transactions for datasets: "ordinary"
transaction (which may be writing as well, but, AFAIK, is used for
reading data), and a separate "writing" transaction. So, you separate
those transactions too: make long-lasting reading transaction with
parameters
read
read_committed
rec_version
nowait
and short-lasting writing transaction
write
concurrency
nowait


--
Best regards,
Pavel Menshchikov
http://www.ls-software.com/