Re: State of data over the time

The performance impact is minimal only if you don't use it. Rule of thumb:

    Rolling back for read consistency is always expensive.     Rolling back more than a short distance is extremely expensive.

(Mind you - my first thought was "you could have fun with flashback for this one")

--
Jonathan Lewis
http://www.jlcomp.demon.co.uk

Host to The Co-Operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html

Author of:
Practical Oracle 8i: Building Efficient Databases

Screen saver or Life saver: http://www.ud.com
Use spare CPU to assist in cancer research.

Howard J. Rogers wrote in message <3b97dd9d_at_news.iprimus.com.au>...


>

>It's part of the database engine, so there are minimal performance impacts,

>and Flashback is read only, so there are no worries about database

>integrity.

>