RE: MS SQL 7.0 to PostgreSQL 7.1

From: "Gordon Runkle" <gar(at)integrated-dynamics(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: RE: MS SQL 7.0 to PostgreSQL 7.1
Date: 2001-05-09 21:34:44
Message-ID: 9dccv7$1i84$1@news.tht.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 2001-05-09 21:37:22 Re: Oracle to Pg tool
Previous Message Vince Vielhaber 2001-05-09 21:28:26 Re: Oracle to Pg tool