Slashdot Mirror

← Back to Stories (view on slashdot.org)

Data Migration from Sybase to PostgreSQL?

Posted by Cliff on from the tools-for-the-trade dept.

hp9000 asks: "I've been asked to work on a project that will involve data migration from Sybase to PostgreSQL. I'd like to know if there's any tool, similar to Oracle's Migration Workbench, or even a shell script, to move all data from Sybase tables to PostgreSQL tables, creating the tables/tablespaces/etc in the process or at least generating a script to do so. Any kind of tool, so to speak, that would allow me to perform the migration will be great. I'm not interested in the sql code migration (that will come later if necessary), only tables, indexes, etc. at this point."

2 of 15 comments (clear)

  1. Just gonna throw this out there... by ClubPetey · · Score: 3, Informative

    By the time you find a tool to help with the migration, learn how the tool works, fix the inevitable quirks, and solve the blantant errors with the software, you could have exported the schema from Sybase, translated it with search/replace by hand, and created the new schema in PostgreSQL for a lot less time and money.

    Once the schemas are setup, you can use any number of raw copy tools out there. Borland Delphi comes with one (DataPamp) there are several java-based ones out there. Or you could just write a series of "INSERT INTO" SQL statements with ODBC. This assumes that you are a competent DBA and not like all those Oracle "experts" out there that can't write SQL.

    --
    Si hoc legere scis nimium eruditionis habes
  2. Moving the Data Is Only Half The Battle by superid · · Score: 3, Informative
    I'm in the same boat. We've got a Sybase installation that has evolved over the past 7 years. It's grown to about 20GB, which I know is really not that big. I don't think I'd have any problem moving the data, as most of our data typing is pretty standard.

    However, we have hundreds and hundreds (my guess is nearly 3000) triggers and stored procedures. Migrating the data is completely useless for me unless we can somehow migrate the T-SQL too....and I strongly suspect thats not gonna happen.

    So, does anyone have any thoughts on this?