Subject | Truncating transaction logs in Firebird in v2.01 - v2.03 |
---|---|
Author | Niben M Singh |
Post date | 2008-04-12T13:31:20Z |
Hello All -
I have tried this on Firebird Database v2.01 and v2.03.
I created new Firebird database with page size 4KB and transferred data using ODBC. This database has about 400 tables and about 500MB size right now. After I created the database I thought about truncating transaction logs.
I sweeped the database using GFIX command as -
"C:\Program Files\Firebird\Firebird_2_0\bin\"gfix -user SYSDBA -password masterkey db_name.fdb -sweep
Then I backedup the database using GBAK with truncate log option as -
gbak -v -t -user SYSDBA -password masterkey db_name.fdb db_name.fbk
I restored the database using GBAK again with the hope of truncating logs as -
gbak -v -c -p 4096 -user SYSDBA -password masterkey db_name.fbk new_db_name.fdb
It brought the size to ~480MB. But when I did this second time same process on this newly backed up database the size went down to ~350MB.
I am hoping this may be due to the reason that some of the transaction were not committed when I created the Firebird file initially. So, I am wondering if there is an easy way of committing all the uncommitted transaction? Or, if there is a process to truncate the transaction log properly?
I will appreciate any responses.
Regards,
Niben
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
[Non-text portions of this message have been removed]
I have tried this on Firebird Database v2.01 and v2.03.
I created new Firebird database with page size 4KB and transferred data using ODBC. This database has about 400 tables and about 500MB size right now. After I created the database I thought about truncating transaction logs.
I sweeped the database using GFIX command as -
"C:\Program Files\Firebird\Firebird_2_0\bin\"gfix -user SYSDBA -password masterkey db_name.fdb -sweep
Then I backedup the database using GBAK with truncate log option as -
gbak -v -t -user SYSDBA -password masterkey db_name.fdb db_name.fbk
I restored the database using GBAK again with the hope of truncating logs as -
gbak -v -c -p 4096 -user SYSDBA -password masterkey db_name.fbk new_db_name.fdb
It brought the size to ~480MB. But when I did this second time same process on this newly backed up database the size went down to ~350MB.
I am hoping this may be due to the reason that some of the transaction were not committed when I created the Firebird file initially. So, I am wondering if there is an easy way of committing all the uncommitted transaction? Or, if there is a process to truncate the transaction log properly?
I will appreciate any responses.
Regards,
Niben
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
[Non-text portions of this message have been removed]