RE: MS SQL 7.0 to PostgreSQL 7.1 - Mailing list pgsql-general

From Gordon Runkle
Subject RE: MS SQL 7.0 to PostgreSQL 7.1
Date
Msg-id 9dccv7$1i84$1@news.tht.net
Whole thread Raw
In response to RE: MS SQL 7.0 to PostgreSQL 7.1  (Jeff Eckermann <jeckermann@verio.net>)
List pgsql-general
In article <08CD1781F85AD4118E0800A0C9B8580B094A74@NEZU>, "Jeff Eckermann"
<jeckermann@verio.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

pgsql-general by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Oracle to Pg tool
Next
From: John Coers
Date:
Subject: COPY locking