Migration between databases almost always involves some serious headaches.

I once migrated a couple of VFP tables to PostgreSQL.  The two vfp 
tables involved were a customer table and A/R transaction table with a 
join on customer number with referential integrity being enforced.

The migration went as follows:

1)  I dumped the two VFP tables into a comma delimited file.

2)  I copied the comma delimited files from Windows to a Linux ext3 file 
system.

2)  I used pgAdmin II, I believe, to create a database with two 
PostgreSQL tables that matched the comma delimited file exactly, using 
the closest matching PostgreSQL field type to hold the comma delimited data.

3)  I used pgAdmin II to import the two comma delimited file to the 
PostgreSQL tables.  PgAdmin constantly complained about dirty data that 
it would not import.

I started out with Notepad to clean up the files after each import 
failure.  The A/R table was to big for Notepad to handle, so I moved the 
comma delimited files to Linux ext3 file system and used VI editor to 
clean up the data.  I must have had 50 failure to import, due to dirty 
data, each requiring a search and replace with the VI editor before 
trying the import again.

4) After finally succeeding in importing the data, I created the 
indexes, primary fields, foreign key constraints, etc.

5)  I modify my VFP client application as needed to connect, select, 
update, add, and delete records in the PostgreSQL server.  For example 
VFP used "yes" or "no" to return a logical value, while PostgreSQL used 
0 or 1.

Migration programs available today to convert MySQL to PostgreSQL may 
handle much of this work, but be prepared to expend some major work and 
time.

Regards,

LelandJ









On 11/07/2010 11:35 AM, Dan Covill wrote:
> Wikipedia for PostgreSQL:
>      http://en.wikipedia.org/wiki/PostgreSQL
> says that a MySQL to PostGRES migration tool is included with each download!
>
> Dan Covill
>
> On 11/6/2010 2:20 PM, Pete Theisen wrote:
>> Hi Everybody,
>>
>> How different are they? Assuming an ordinary geek who administers the
>> MySQL with occasional problems, is it impossible, hard or easy.
[excessive quoting removed by server]

_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to