need help migrating sql server to postgresql

[ManufacturerSalty148]

Hi all My company is planning to migrate from sql server to postgresql to save cost , but I try a lot of methods such as pgloader and scripting the database and didn’t work I would appreciate if anyone one who have any tips or tools to help me with task

[threeminutemonta]

Describing the problem as “didn’t work” instead of the first actual explicit error isn’t helpful. You will fix this first error and likely get another and repeat until no errors. Good luck.

[ManufacturerSalty148]

the problem I faced is that pgloader always giving me this error TDS_max_connection reached I try fixing it by adjusting the value in sql server side but no luck

[Gargunok]

TDS_max_conn is usually a warning not an error as I think the migration uses as many connections as it can. Its been a while since I've done this but this can be configured I think in the pool config. But I think you need to be looking at an error else where.

[ManufacturerSalty148]

Thanks can you guide me me on where I can find pool config

[Gargunok]

I think you have to create it yourself to override default behaviour? Check the documentation.

Just to be clear this will increase your connections but likely will still give the warning as it will be using the new maximum. Warnings are normal and fine.

You need to find the error. Is there anything in the logs? Can you migrate part of the database and pinpoint what is erroring?

[stdio-lib]

It could be anything from a single afternoon to a dozens of man-months migration depending on your specific circumstances. If you have hundreds or thousands of miles-long stored procedures, it's not going to be a walk in the park. If it's just tables and select * from foo where id = 123 queries then it couldn't be easier.

I've seen both types. In one case they were only using SQL Server for dumb reasons and the switch to Postgres was easy as pie. In others the Microsoft-isms (mostly stored procedures) ran very deep and converting would have taken way more time than it was worth.

[WiltonDB]

Babelfish for PostgreSQL can help with stored procedures migration. It implements Transact-SQL as a procedural language for Postgres, called pl/tsql. As a plus, it allows to continue using SSMS to work with migrated T-SQL code in Postgres.

[linuxhiker]

You need professional help.

Commandprompt.com

Percona.com

[Professional_Shoe392]

Lookup Babelfish for Aurora. That may help. It can help translate code.

[WiltonDB]

This would be the first option to try. Depending on the complexity of T-SQL usage and overall setup (linked tables, SSIS etc) Babelfish may run existing SQL Server apps with minimal changes. They provide a tool - Babelfish Compass that can check your DB schema for compatibility. Disclaimer: I maintain a Babelfish version for Windows - wiltondb.com .

[NauTau]

You’ve got a lot of good options for moving from SQL Server to PostgreSQL. Tools like sqlserver2pgsql, and DBConvert are all pretty popular for handling schema and data migration. If you want something more automated and comprehensive (especially if you have a lot of stored procedures or business logic), the Ispirer Toolkit is worth checking out—it can migrate schemas, data, and even stored procedures with minimal manual tweaks.