Re: [firebird-support] Why a database grows after a cycle backup/restore?

2013-06-21 Thread Alexey Kovyazin
Hi Walter, C:\Archivos de programa\Firebird\Firebird_2_5\bin\Gbak -c -v -t -rep -p 8192 -user SYSDBA -password masterkey D:\RestaurarBASES\BDRestaurada\BASE.GBK 127.0.0.1:D:\RestaurarBASES\BDRestaurada\BASE.FDB -FIX_FSS_D ISO8859_1 -FIX_FSS_MISO8859_1 This is the answer why database

Re: [firebird-support] Why a database grows after a cycle backup/restore?

2013-06-19 Thread Stefan Heymann
The source database has 3.1 Gb but after the backup/restore have 4.2 Gb Did you specify a larger page size for the restore? Regards Stefan

[firebird-support] Why a database grows after a cycle backup/restore?

2013-06-18 Thread W O
Hello everybody Which can be the cause that a database of 3.1 gigabytes grows to 4.2 gigabytes after a cycle backup/restore? The file FIREBIRD.CONF seems normal, nothing strange there. Growing 1.1 gigabytes seems to me too much. Greetings. Walter. [Non-text portions of this message have

RE: [firebird-support] Why a database grows after a cycle backup/restore?

2013-06-18 Thread Leyne, Sean
Walter, Which can be the cause that a database of 3.1 gigabytes grows to 4.2 gigabytes after a cycle backup/restore? The file FIREBIRD.CONF seems normal, nothing strange there. Growing 1.1 gigabytes seems to me too much. To be clear, it is source database or the backup file 3.1GB? Sean

Re: [firebird-support] Why a database grows after a cycle backup/restore?

2013-06-18 Thread W O
The source database has 3.1 Gb but after the backup/restore have 4.2 Gb Seems very strange for me. Greetings. Walter. On Tue, Jun 18, 2013 at 6:03 PM, Leyne, Sean s...@broadviewsoftware.comwrote: ** Walter, Which can be the cause that a database of 3.1 gigabytes grows to 4.2

Re: [firebird-support] Why a database grows after a cycle backup/restore?

2013-06-18 Thread Alexandre Benson Smith
Em 18/6/2013 19:44, W O escreveu: The source database has 3.1 Gb but after the backup/restore have 4.2 Gb Seems very strange for me. Greetings. Walter. Just a shot in the dark... Could be that the original database was restored with -USE_ALL_SPACE and the new database was not be