2013/4/5 Robert Treat <rob@xxxxxxxxxx>: > > 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 -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
