Subject RE: [firebird-support] Firebird Database Partition
Author Svein Erling Tysvær
Generally, I think of the Firebird database files as a black box and trust Firebird to treat them appropriately as long as file system limits aren't reached.

You could theoretically put your image tables in a separate database. Firebird does support multiconnection transactions, so it is possible to have transactions that span several databases and that either commit or roll back as a whole (i.e. they will not succeed on one database and fail on the other). Multiconnection queries aren't possible, so (at least in theory) you cannot write a query that join tables in different databases. I say in theory, since Firebird 2.5 has the possibility of contacting other databases through EXECUTE STATEMENT and having EXECUTE STATEMENT within a stored procedure that your query joins to could possibly work (note that I have never used Firebird 2.5 and don't know the pitfalls).


-----Original Message-----
From: [] On Behalf Of D K
Sent: 19. januar 2010 22:17
Subject: [firebird-support] Firebird Database Partition

I have large number of tables in my database and some table sizes like image tables are very heavy due to its size.So is there any way to partition the firebird database in such a way that i load very heavy tables in one disk and others in other disk.