Re: RE: MS SQL 7.0 to PostgreSQL 7.1

From: Justin Clift <justin(at)postgresql(dot)org>
To: Gordon Runkle <gar(at)integrated-dynamics(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: RE: MS SQL 7.0 to PostgreSQL 7.1
Date: 2001-05-10 12:56:40
Message-ID: 3AFA9008.27B84F1C@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi all,

If someone wants to create a script and article for doing conversions
from MS SQL Server to PostgreSQL, this would be Really Beneficial. If
it needs to be hosted somewhere, then it can be put on
techdocs.postgresql.org (or elsewhere as the author wishes, with a link
to it on techdocs).

:-)

Regards and best wishes,

Justin Clift

Gordon Runkle wrote:
>
> In article <08CD1781F85AD4118E0800A0C9B8580B094A74(at)NEZU>, "Jeff Eckermann"
> <jeckermann(at)verio(dot)net> wrote:
>
> > Also:
> > * Watch out for embedded tabs and carriage returns in your data: these
> > will cause problems during or after your COPY into PostgreSQL. * Check
> > the value used in the exported file to represent NULL values (could be
> > an empty string, or "NULL", or something else), and use that in your
> > COPY statement: "COPY table from stdin with null as 'whatever';"
>
> My experience is that MSSQL7 will export (bcp) NULLs
> as an ASCII zero character. Not pretty. You'll want
> to put together a little PERL script to fix that.
>
> Gordon.
> --
> It doesn't get any easier, you just go faster.
> -- Greg LeMond
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster

--
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
- Indira Gandhi

In response to

Browse pgsql-general by date

  From Date Subject
Next Message martin.chantler 2001-05-10 13:06:19 Re: ER diagrams
Previous Message Michelle Murrain 2001-05-10 12:54:49 Re: GRANT