From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | cosmin ioan <oracos(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: moving data to from ms sql server via SSIS |
Date: | 2018-08-15 18:09:10 |
Message-ID: | e6b8090e-8ac9-16ad-6148-589796add37e@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 08/15/2018 11:03 AM, cosmin ioan wrote:
> hi folks,
> we're trying to phase out MS SQL Server and we're trying to understand
> the easiest way to move data from MS SQL Server to postgres, via SSIS,
> say via ODBC, OleDB or .Net drivers, and basically create new tables &
> move data, into the target postgres db. What drivers would be the
> best/most flexible?
>
> thanks much for any info or white papers on the topic,
A *lot* of this is: it depends
However, a pretty simple way is to use either FDWs from PostgreSQL or
linked tables in MSSQL. It would be easy enough for example to have
table ms.foo which has data and then table postgres.foo that is empty.
If ms.foo is linked (or and FDW table) you can use standard SQL to do
things like INSERT INTO (SELECT * FROM).
Of course if you can take the outage and you prep PostgreSQL
appropriately you could also just dump out to csv or tab delimited files
and load them with COPY.
JD
--
Command Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc
*** A fault and talent of mine is to tell it exactly how it is. ***
PostgreSQL centered full stack support, consulting and development.
Advocate: @amplifypostgres || Learn: https://postgresconf.org
***** Unless otherwise stated, opinions are my own. *****
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2018-08-15 19:22:10 | Re: Code of Conduct plan |
Previous Message | cosmin ioan | 2018-08-15 18:03:07 | moving data to from ms sql server via SSIS |