Subject | Re: Newbie: Posgres to Firebird |
---|---|
Author | h_urlaf |
Post date | 2004-02-22T10:23:37Z |
--- In firebird-support@yahoogroups.com, "jofell_xcite"
<jofell_xcite@y...> wrote:
a number of tools that might help with your migration. I'm working on
a migration that will consolidate 5 loosely coupled access databases,
a handfull of text files, and some data in the registry to a single
database, for which I'm writing my own tool to do the data pumping.
Took me a few days.
The largest problem I've met so far had to do with compensating for
different features or approaches between access and mysql on the one
side (which is what we've used so far) and Firebird on the other side,
things like auto-increment fields, stuff you can/must do with stored
procedures in FB, indexing limitations, and some other stuff. From my
admittedly limited experience I would advice you to get your DB schema
in FB to do what you want first, then think about how you are going to
pump the data.
But a smooth transition with zero changes to the data and client apps
would have to be for very simple apps, I'd venture to guess. If you
use any of the special PostgrSQL features you'll certainly have some
work to do.
Out of curiousity, why are you moving from PostgreSQL to Firebird?
<jofell_xcite@y...> wrote:
> Anybody here who had migrations from Postgres to Firebird? I've heardhttp://www.ibphoenix.com/main.nfs?a=ibphoenix&page=ibp_mig_tools lists
> such MIGRATIONS give a lot of MIGRAINES, and the only google match
> for "PostgresQL to Firebird" was just a babble about RDBMS's.
>
> How should I start? What tools can I use? Are there easier ways than
> exporting all records to csv and then uploading them to Firebird...
> or I guess if that was a solution?
a number of tools that might help with your migration. I'm working on
a migration that will consolidate 5 loosely coupled access databases,
a handfull of text files, and some data in the registry to a single
database, for which I'm writing my own tool to do the data pumping.
Took me a few days.
The largest problem I've met so far had to do with compensating for
different features or approaches between access and mysql on the one
side (which is what we've used so far) and Firebird on the other side,
things like auto-increment fields, stuff you can/must do with stored
procedures in FB, indexing limitations, and some other stuff. From my
admittedly limited experience I would advice you to get your DB schema
in FB to do what you want first, then think about how you are going to
pump the data.
But a smooth transition with zero changes to the data and client apps
would have to be for very simple apps, I'd venture to guess. If you
use any of the special PostgrSQL features you'll certainly have some
work to do.
Out of curiousity, why are you moving from PostgreSQL to Firebird?