Q:What kind of system is this? .The response is on Firebird-support
Monitoring software with also web access by many many users ~1 000 000
They do something which need transaction and some select(reports) which “not need” transaction
but in transactional database select also start short transaction then i can not remove it creation..
1 000 0000 x 10 queries per day i got 10 000 000 transaction+ system self generate 8 000 000 transaction per day (to
storing/updating/computing.. data)
and Forced Writes are ON but database work on some not mechanical device like normal HDD and corruption is reduced to minimal possible but this transaction counter do may problem :/
In a recent survey for the next Firebird Developers Day in Brazil, one of the questions was about the average size of the participants (and/or their customers) databases. A total of 344 people answered, and the result can be seen below:
In general, your (or your customer’s) database has…
Percent
Count
Answers
20.3%
70/344
up to 500MB
31.1%
107/344
up to 2GB
20.9%
72/344
up to 5GB
17.2%
59/344
up to 10GB
10.5%
36/344
more than 10GB
100.0%
344/344
Summary
PS: Note that this survey was directed only to people who intends to participate in the next Brazilian FDD edition.
Some time ago I’ve written a portal in pure PHP for controlling test laboratory of C# applications. The whole testing process is based on a framework of our own production.
Omega Sync can compare and synchronize both database schema and table data.
You can even synchronize data of heterogeneous databases (for example, compare your local Firebird database with a MySQL replica on your web site – and synchronize all the differences in just a few minutes). http://www.spectralcore.com/omegasync/
Philippe Makowski managed to rebuild the flamerobin 0.9.2 package for fedora 15 also for the 16 version too .
There were some issues with new strict compiler rules in fedora similar with what happened when we tried to compile
flamerobin with clang
Notes on Paul Beach blog about forced writes on Linux/Windows and the config setting (how it was ignored on linux on older versions of firebird)
The issues are solved on firebird > 2.0.4 or firebird >=2.1.0 final , also forced writes should be left on if you don’t need corrupted db