It's only about 20 tables -- so creating them by hand in M(S/Y)SQL wouldn't
take too long.
I still need to get the data into PostGreSQL though before I can run my own
export though. I'm using the pgAdminIII tool to try to import the script,
but I am (sadly) getting strange results when running the import. Maybe I'm
going about this the wrong way:
Right click my database >> choose CREATE script
Click the "Open" folder button and select my .out file
Click the Execute button
It chugs for a good 2 or 3 minutes (fine by me, it's a 50 meg file it's got
to parse and execute) -- but at the end, it doesn't give any confirmation of
failure or success. I open up my database, and it's still completely empty
-- no table structure or data. I'm wondering if it's a problem with the
.out dump, or my process of importing... any ideas?
Jonathon
-----Original Message-----
From: Sean Davis [mailto:sdavis2@mail.nih.gov]
Sent: Friday, September 14, 2007 1:54 PM
To: Jonathon Stierman
Cc: pgsql-novice@postgresql.org
Subject: Re: [NOVICE] import a .out file
Jonathon Stierman wrote:
> Yep, it definitely is a SQL dump -- it looks much the same as .sql
> files that I'm used to dealing with on MYSQL databases.
>
> Do you have any favorite translator tools that I could look in to?
> The file is massive (58 megs worth) and going through it by hand would
> be quite tedious.
>
> I did find this on the MYSQL homepage:
> http://solutions.mysql.com/solutions/partner.php?partner=1881&other=1
> Suggesting some commercial options are available. Have any of you
> used this tool, or other tools, with success?
>
> Thanks Sean, Sibte, & Richard for your help thus far -- it is most
> appreciated!
How many tables? If it is just a few, I would ask for tab-delimited text
files from postgres and then design the database in mysql or mssql to match
the postgres database. SQL::Translator for perl is one option, but it
usually requires some hand-editing, also.
Sean
