S
Steven Peeters
Guest
You might also want to test the performance of deleting a large number of records in a single transaction vs deleting one record at a time. We followed instructions from KB P36834. (splitting up transactions) However this was still causing BI growth. I then tried to investigate the potential effects on a test-db of large BI growth and backing out of the transaction by using a not-realistic one-big-transaction code, resulting in crash that is the subject of this thread. I'm stull puzzled as of why the BI was growing when I was batching the deletes in 10000 per transaction. In this regard I found the following in KB 15124: Sometimes there is no way to avoid the .bi file being extended; there just isn't enough time to commit transactions and make the cluster available before it is needed again by other transactions. I guess we'll just manually split up our deletes by adjusting the query. (We don't archive records that often)
Continue reading...
Continue reading...