If you could use foreign data wrapper to connect
https://github.com/tds-fdw/tds_fdw then you can skip the migration back and
for to CSV.
You could even do partial migrations if needed (it could impact some
queries' speed though).
Pablo
On Fri, May 3, 2019 at 6:37 AM Adrian Klaver
wrote:
> On
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
On 5/3/19 6:09 AM, Matthias Apitz wrote:
El día Friday, May 03, 2019 a las 07:38:23AM -0500, Ron escribió:
On 5/3/19 6: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
El día Friday, May 03, 2019 a las 07:38:23AM -0500, Ron escribió:
> On 5/3/19 6: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,
## Matthias Apitz (g...@unixarea.de):
> Re/ the migration of the data itself, are there any use case studies
> which could we keep in mind?
https://wiki.postgresql.org/images/e/e7/Pgconfeu_2013_-_Jens_Wilke_-_Sybase_to_PostgreSQL.pdf
Regards,
Christoph
--
Spare Space
On 5/3/19 6: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
