From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | "Hajek, Nick" <Nick(dot)Hajek(at)vishay(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Database Conversion |
Date: | 2008-09-04 16:27:33 |
Message-ID: | dcc563d10809040927x6d9ea5e1m28b89678a0ef4051@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Thu, Sep 4, 2008 at 9:22 AM, Hajek, Nick <Nick(dot)Hajek(at)vishay(dot)com> wrote:
>
>>
>> Hello, All,
>>
>> I have a new faculty member who has a large database that is
>> in MySQL. We don't support MySQL so the database needs to be
>> ported to PostgreSQL. Her GA, who know MySQL, says that he
>> has a query that he will run that will put the data into
>> postgres. I thought that the data would have to be output to
>> a text file and then copied into postgres. I don't know
>> MySQL. I've done a conversion from Oracle and this is how I
>> did it. Is he correct that he can put the data into a
>> postgres database by running a MySQL query? It doesn't sound
>> possible to me.
>>
>> Carol
>>
>
> You could possibly do it in a single operation using MS Access if you
> have an ODBC connection to each database. If however the dataset is
> large, I wouldn't recommend it. I have a number of MySQL and PostgreSQL
> dbs and I either dump sql and then import or use PHP scripts when moving
> between the two.
Also, if you can spare the afternoon to learn it, sed is an awesome
tool for ETL. I've used it for migrating stuff from oracle to pgsql
and mangling input data to work.
From | Date | Subject | |
---|---|---|---|
Next Message | Carol Walter | 2008-09-04 16:45:50 | Re: Database Conversion |
Previous Message | Scott Marlowe | 2008-09-04 16:25:42 | Re: Help! |