Re: Re: [firebird-support] Update big table and nbackup benefit or not?

W dniu 2016-04-05 12:45:34 użytkownik Dimitry Sibiryakov s...@ibphoenix.com [firebird-support] napisał: > 05.04.2016 12:43, liviuslivius liviusliv...@poczta.onet.pl [firebird-support] > wrote: > > but what happens at merge stage (delta merging) when i unlock

Re: [firebird-support] Update big table and nbackup benefit or not?

05.04.2016 12:43, liviuslivius liviusliv...@poczta.onet.pl [firebird-support] wrote: > but what happens at merge stage (delta merging) when i unlock database? > page will be overriden or new one will be created and old will be marked as > empty? Old pages will be overwritten, new ones will

Re: [firebird-support] Update big table and nbackup benefit or not?

05.04.2016 10:21, liviuslivius liviusliv...@poczta.onet.pl [firebird-support] wrote: > what is the answer for this A or B? None of them. Full pages are written to delta file, so you'll have database in exactly the same state as per scenario 1. -- WBR, SD.

Re: Re: [firebird-support] Update big table and nbackup benefit or not?

Hi,   thanks Tim for warning - i know fragmenting records are bad but in my case this probably not happen because this is ppmxl database with numbers only    but do you know what will be answer A or B? If no one answers I'll have to test yourself ;-)   regards, Karol Bieniaszewski     If the

Re: [firebird-support] Update big table and nbackup benefit or not?

If the update makes the records longer (after run-length encoding) it's even more fun, as you might get fragmentation (of records across pages) and access times can then increase by a very large factor indeed, even to the extent of completely crippling the performance of an entire application.

[firebird-support] Update big table and nbackup benefit or not?

Hi,   i must update big table 100 GB and as we know when we do update then new record version will be created. scenarion 1:   1. Table size 100GB (db size 200GB) 2. Update field in all records generate 100GB new record versions 3. table size after is 200GB (db size 300GB) 4. sweep remove 100GB and