migrate data from MS SQL to PostgreSQL?

I’ve looked around and can’t seem to find anything that answers this specific question.

What is the simplest way to move data from an MS SQL Server 2005 DB to a Postgres install (8.x)?

  • Rebuilding large SQL indexes isn't changing the fragmentation percentage
  • Design pattern to convert tree-rules from Weka into SQL query
  • How do I achieve this sort of replication?
  • Why is Entity Framework calling my stored procedure but returning an incorrect value?
  • How to get rid of deadlock in a SQL Server 2005 and C# application?
  • simple error on datetime column
  • I’ve looked into several utilities like “Full Convert Enterprise”, etc, and they all fail for one reason or another, ranging from strange errors that make it blow up to inserting nulls rather than actual data (wth?).

    I’m looking at a DB with all table except for a single view, no stored procs, functions, etc.

    At this point I’m about to write a small utility to do it for me, I just can’t believe that’s necessary. Surely there’s something somewhere that can do this? I’m not even too worried about cost, although free is preferable 🙂

    3 Solutions collect form web for “migrate data from MS SQL to PostgreSQL?”

    Take a look at the Software Catalogue. Under Administration/development tools I see DBConvert for MS SQL & PostgreSQL. Probably there are other similar tools listed.

    You can use the MS DTS functionality (renamed to SSIS in the latest version I think). One issue with the DTS is that I’ve been unable to make it do a commit after each row when loading the data into pg. Which is fine if you only have a couple of 100k rows or so, but it’s really very slow.

    I usually end up writing a small script that dumps the data out of SQLServer in CSV format, and then use COPY WITH CSV on the PostgreSQL side.

    Both those only take care of the data though. Taking care of the schema is a bit harder, since datatypes don’t necessarily map straight over. But it can easily be scripted together with a static load of the schema. If the schema is simple (just varchar/int datatypes for example), that part can also easily be scripted off the data in INFORMATION_SCHEMA.

    Well there are .NET bindings for MS SQL Server 2005 (obviously) and also for PostgreSQL. So it would only take a few lines of code to code up a program that could transfer data safely from one to the other. The view would probably have to be done manually as Postgres doesn’t use the same language for views as SQL Server.

    MS SQL Server is a Microsoft SQL Database product, include sql server standard, sql server management studio, sql server express and so on.