From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Matthias Apitz <guru(at)unixarea(dot)de>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Migrating database(s) from Sybase ASE 15.7 to PostgreSQL 10.6 on Linux |
Date: | 2019-05-03 13:36:51 |
Message-ID: | bac2bddf-9c4a-dcf1-273e-dbf493d9c932@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 5/3/19 4:56 AM, Matthias Apitz wrote:
>
> Hello,
>
> We're investigating the migration of our LMS (Library Managment System)
> from Sybase ASE 15.7 to PostgreSQL 10.6. The used database in field have
> around 400 columns, some of them are also containing BLOB (bytea) data.
> The DB size vary upto 20 GByte. The interfaces contain any kind of
> language one could imagine :-) ESQL/C, JDBC, Perl DBD, ...
>
> Re/ the migration of the data itself, are there any use case studies
> which could we keep in mind? We plan to export the tables with our own
> tool which produces CSV with delimiter '|' (and \| if the char | is in
> char columns too) and with hex representation of the BLOB data. This seems
> to fit nicely with PostgreSQL's COPY command.
You might want to also take a look at:
A PostgreSQL foreign data wrapper to connect to TDS databases (Sybase
and Microsoft SQL Server)
https://github.com/tds-fdw/tds_fdw
>
> Any known pitfalls?
>
> Btw: We're investigating MySQL too, but this seems to be from the list
> now for not having an ESQL/C interface.
>
> Regards
>
> matthias
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2019-05-03 13:46:41 | Re: Update row attribute that is part of row level security policy using_expression |
Previous Message | Daniel Verite | 2019-05-03 13:35:47 | Re: Upgrading locale issues |