no-integrity flag on big transactions still bi file grows

Posted by Peter Willer on 13-Jun-2017 11:56

Hello,

just for understanding: Why is the bi file size growing when doing big transactions with no-integrity flag?

For example importing a schema delta file with a new index on a huge table.

Thank you

Regards

Peter 

Posted by ChUIMonster on 13-Jun-2017 12:36

If you are thinking that -i = "no bi notes" then you have fallen victim to mythology.

The bi notes are created, even  with -i, because the 4gl may need to UNDO a transaction.

BTW -- you get essentially identical performance benefits using -r and it is less fatal if something goes wrong.  Neither should be used without first making a backup but if you are going to do something like that -r is safer.

All Replies

Posted by George Potemkin on 13-Jun-2017 12:33

Progress creates the same recovery notes and the same number of the recovery notes with/without no-integrity flag.

You need the -ii parameter but it's not (yet?) implemented. ;-)

Posted by Rob Fitzpatrick on 13-Jun-2017 12:34

No-integrity (-i) doesn't mean "no BI notes".  While crash recovery is not possible with -i, transaction undo is; so BI notes must still be written.

A better practice when adding an index to a very large table is to add it inactive and then activate or build it after the fact.  The schema update will then be very quick and will not grow the BI file.

Posted by ChUIMonster on 13-Jun-2017 12:36

If you are thinking that -i = "no bi notes" then you have fallen victim to mythology.

The bi notes are created, even  with -i, because the 4gl may need to UNDO a transaction.

BTW -- you get essentially identical performance benefits using -r and it is less fatal if something goes wrong.  Neither should be used without first making a backup but if you are going to do something like that -r is safer.

Posted by Peter Willer on 13-Jun-2017 12:39

Thank you all for the quick replies.

All answers answered the question.

Regards

Peter

This thread is closed