Subject | Single fdb or multiple fdb's |
---|---|
Author | Ray Jenkins |
Post date | 2004-11-11T20:39:56Z |
Sorry hit reply to the other topic and forgot to change the subject line...
I am starting to move all the in-house apps to Firbird. They have been
running on Clipper and Paradox database systems.
My question is this...
How do I structure the new Database? Do I have one single fdb file and
just throw all the tables in the same db, or do I split it out into
some logical transaction based groupings? If I split it into multiple
fdb files can they all reside in the same directory or should I
seperate them into different subdirectories.
Right now the Firebird server is on MS 2000 server but we will be
moving them to a Linux server as soon as our IT guy can get the server
built. (You know how those IT guys are busy putting out fires)
Any input would be apreciated.
Thanks
Ray
I am starting to move all the in-house apps to Firbird. They have been
running on Clipper and Paradox database systems.
My question is this...
How do I structure the new Database? Do I have one single fdb file and
just throw all the tables in the same db, or do I split it out into
some logical transaction based groupings? If I split it into multiple
fdb files can they all reside in the same directory or should I
seperate them into different subdirectories.
Right now the Firebird server is on MS 2000 server but we will be
moving them to a Linux server as soon as our IT guy can get the server
built. (You know how those IT guys are busy putting out fires)
Any input would be apreciated.
Thanks
Ray