Skip site navigation (1) Skip section navigation (2)

Re: Database conversion

From: Chris Carbaugh <cjtech(at)blazenet(dot)net>
To: brad <brad(at)kieser(dot)net>
Cc: Max Pyziur <pyz(at)panix(dot)com>, pgsql-admin(at)postgresql(dot)org
Subject: Re: Database conversion
Date: 2000-04-16 22:35:48
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
Check out the ODBC driver on the PG site.  Quite simple really.  Just
load the driver on your Win Box, and create the DSN.

Now all you have to do is open Access, and export your tables via ODBC. 
I have only done this a few times with rather simple databases, but
haven't had any troubles.

It create both the table definition and the data in the Postgres DB.

With Win98 and Access2000 running in a VMWare machine under RedHat6.0, I
can't imagine an easier conversion.  I actually exported the Access
tables via ODBC from one VMWare machine to another VMWare machine
running RedHat6.1, PostgreSQL, and PHP.


If this message doesn't get to the mailing list, would either Brad or
Max forward it there.  I think my ISP has a goofy email Alias config.

brad wrote:
> I have had problems with the pg_dump command, though, when the tables have
> been wide (many columns with long text items in them) and deep (many rows).
> The pg_dump utility reloads the data from the stdin, using a pipe.
> This doesn't work too well (i.e. no data gets loaded) for these tables, but
> is fine for smaller tables.
> I use linux - nearly every release of kernel 2.0 and 2.2.
> Max Pyziur wrote:
> > Steve Murphy wrote:
> > >
> > > Hi,
> > >
> > > Does anyone know of any conversion programs that will either convert an
> > > MS Access database file to a Postresql database or from a Filemaker Pro
> > > database file to a Postresql database for the Red Hat Linux OS?
> > >
> > > Any help or educated guesses of where to start looking would be
> > > extremely welcome.
> >
> > Apologies that this reply is coming possibly a bit late.
> >
> > My experience is essentially limited to Postgres, Informix, and
> > Foxpro, the last in which I haven't done any development in a while.
> >
> > General procedure that I know of is:
> > 1 - dump the schema of one to a file and tweak it so that it conforms
> > to the standards of the target database server
> > 2 - dump the data to a pipe-delimited text file
> > 3 - use the schema from the source database program to create a
> > database in the target database program/server
> > 4 - import the pipe-delimited data.
> >
> > In the case of Informix and Postgres, both have utilities (dbschema
> > and pg_dump with the -s flag, respectively) which allow you to output
> > a databases schema to stdout or a file.  I know that with Foxpro 3.0
> > there was some sort of schema utility included somewhere.  Informix
> > has an SQL command called UNLOAD which allows you to dump data to
> > pipe-delimited formats; pg_dump -a dumps the data in postgres; COPY in
> > the postgres monitor gives you a little more control as to the format
> > of data dump.  Informix's syntax is a cleaner implementation in this
> > regard, though.  Postgres's pg_dump is great, though, for backing up a
> > whole database w/ schema and restoring it.
> >
> > So I only gave you half an answer since I didn't address your MS
> > Access or Filemaker pro issues.  I suspect though you can do exports
> > and control the format in some way.
> >
> > > Thanx, Steve.
> >
> > --
> > Max Pyziur                                     BRAMA - Gateway Ukraine
> > pyz(at)brama(dot)com                        

In response to

pgsql-admin by date

Next:From: Joe ConwayDate: 2000-04-17 03:02:32
Subject: pg_dump error
Previous:From: bradDate: 2000-04-16 20:40:08
Subject: Re: Database conversion

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group