Is there any way to disable rollback either on a single transaction or
on the entire database? I can't tell you how many times during the
design and testing phase of our data warehouse project that rollback
segments have become a real pain in the neck! There are times that it
seems like the database gets in our way more than it helps us and it's
almost always to do with rollback segments.
We are still at a point in our project where there are no users on the
system. Just one developer. I don't know the proper terminology, but
there's got to be some way to tell the database we don't care about
rolling back transactions, or concurrency issues. Actually, even when
the database goes live we won't care about this because it's a data
warehouse, nothing ever changes except for one weekend per month and
during that time the database will be inaccessible.
Received on Mon Jul 31 1995 - 00:00:00 CEST
