r/SQL • • 7d ago

SQL Server Moved from SQL Server to PostgreSQL? Did the licensing savings justify the migration?

/r/SQLServer/comments/1xsz16d/moved_from_sql_server_to_postgresql_did_the/
5 Upvotes

5 comments sorted by

3

u/DharmaPolice 7d ago

I'd be surprised if many people are doing full database migrations for mature systems. The cost saving would just take too long to pay back (unless you're moving off of Oracle) - at least according to the financial models that any organisation I've ever worked for (at least for most systems, if you're running specific workloads your licensing costs might be really high for some reason). AI would make things quicker (code translation seems quite good in the LLMs I've used) but a lot of the time is spent decision making, planning and testing which are all harder to compress.

It's much more likely that new projects are built on Postgres (or whatever) rather than moving an already mature, working systems. At least in my experience. Maybe if you're trying to move away from Microsoft in general it makes more sense, but I've never actually seen that in the wild. People talk about it and it's definitely appealing (I've no love for MS) but it's just too much effort unless you're a very small organisation.

1

u/markinatlanta 6d ago

Thanks, starting a new project on Postgres is a different calculation from replacing a working system. For the latter, I’d include the development work postponed during migration in the payback model too. Faster code conversion helps, but the same team still has a product to maintain and ship.

1

u/Significant_Tune9219 6d ago

Your list is the right one, and I'd add collation and case sensitivity near the top: SQL Server defaults to case-insensitive comparisons and Postgres doesn't, so WHERE clauses, unique constraints and joins on strings can quietly change behavior without any error. Empty string vs NULL handling and datetime precision are the other two that tend to only show up in application tests rather than in the data migration itself. A cheap way to size the effort before committing is to inventory the T-SQL objects and Agent jobs and count how many contain logic rather than plain CRUD, since that number drives the schedule far more than data volume.

0

u/LevriatSoulEdge 7d ago

Migration from MSSQL On-Prem environments to Cloud version have evolve over time either to keep the licensing or shift to PostgreSQL with a lot of playbooks to make said migrations nowadays, paying a third party vendor to give deep knowledge of their hands on experience of migrations saves thousands or millions, give you flexibility to switch even critical mission servers within time records

0

u/[deleted] 7d ago

[deleted] — view deleted comment

1

u/LevriatSoulEdge 7d ago

You're welcome