Schema Conversion from SQL server to Postgresql or other

Question

As an organization, we are struggling economically, so I want to at least save us some cost. I realized that we have an RDS instance running SQL server standard edition which cost us up to 6.5k USD/month. I have realized that the same instance size cost half if it's running a different database engine like Postgresql.

Should I suggest doing schema conversion just to cut costs? Or it sounds insane?

What are the bottlenecks, and caveats in this kind of change?

Should I suggest doing schema conversion just to cut costs? Or it sounds insane?

What are the bottlenecks, and caveats in this kind of change?

Accepted Answer

Hi, you have a comprehensive guide for such a migration here: https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_Source.SQLServer.ToPostgreSQL.html

But, my personal experience (I work in migration domain) is "migrating is testing": for mission-critical workloads, you need very thorough tests to ensure functional equivalence.

So, before proposing such a migration, think about you testing plan to make sure that this migration does not alter your business results.  I would suggest you to read this article to inventory all areas to deal with in preparing such a journey: 
https://www.enterprisedb.com/blog/microsoft-sql-server-mssql-vs-postgresql-comparison-details-what-differences

On your other question, AWS SCT is the tool to convert your db schema from SQL Server to Postgresql: https://aws.amazon.com/dms/schema-conversion-tool/

Schema Conversion from SQL server to Postgresql or other

Relevant content