From: | Martín Marqués <martin(dot)marques(at)gmail(dot)com> |
---|---|
To: | Robert Treat <rob(at)xzilla(dot)net> |
Cc: | Szymon Guz <mabewlun(at)gmail(dot)com>, Roy Anderson <roy(dot)anderson(at)gmail(dot)com>, PostgreSQL <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Oracle to PostgreSQL transition? |
Date: | 2013-04-06 02:59:15 |
Message-ID: | CABeG9LvpfUUQdGBQzE_na5+4CEVD8J0DZHz8jGyLpwx9BK2PXA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
2013/4/5 Robert Treat <rob(at)xzilla(dot)net>:
>
> Yeah, it's worth reading through those links to get an idea of things;
> you'll find much less literature (and tools) for MSSQL, but the
> principals are mostly the same. One thing to decide on is if you are
> going to port applications wholesale, or try to run some kind of
> hybrid oracle/mssql -> postgres mix. If it's the latter, you'll
> probably need to write your own tools; at least we've always done that
> as we've never found anything that worked with both Oracle and MSSQL
> into Postgres reliably; but really it shouldn't be too difficult;
> basically just ETL or some home brew replication scripting to glue
> things together.
I gave some training a few years ago for devs that were migrating from
SQLServer to PostgreSQL and they had a bunch of SP, some of easy
resolution, and others that where impossible with PG functions written
in plpgsql. They used CURSORS a lot to simulate what they did with
SQLServer (there was a better solution, but time was crucial, and they
decided for that approach)
--
Martín Marqués
select 'martin.marques' || '@' || 'gmail.com'
DBA, Programador, Administrador
From | Date | Subject | |
---|---|---|---|
Next Message | Jasen Betts | 2013-04-06 03:32:57 | Re: bug in COPY implementation (all versions of Postgres)? |
Previous Message | John R Pierce | 2013-04-06 00:25:15 | Re: ERROR: SERVER CLOSED THE CONNECTION UNEXPECTEDLY |