More than four months now, since I started using Firebird, and it proved that it is really a competitive option.
I realized now, after this long time, what happened and made me start this thread.
If you are not handling your DB properly you get some issues, which confuses you, and you end up uncertain whether it is your application to blame or the DB performance. In most cases it will be the application (coding).
When I tested the DB from the memory stick and the DB file was disappeared at sudden it seems like the DB was still preserving open transactions and hence the very next connection the server points to WriteFile/ReadFile error. But I had to connect/disconnect several times for the DB to close the transaction, I can't say for sure I know the right way to recover from that (Lost DB File while connection is active) but sure there is a way to test such ungraceful actions and do repair before connecting.
Also I have a new concern, which is the DB file size, not sure how it will be like when working with several GB (probably more than 10GB) DB file. I know there are case studies of hundreds GBs DB files but having experience in DBs I can tell, your 1TB can perform better than someone else's 1GB, and the factor is not only how you setup your DB, there might be many others.
Does anyone have had some +/- experience on this, or advice?