> I was wondering if anyone has any tips that are specific for SQL Server users? Best features? Known issues? Common rebuttals?
Are you talking about SS to PG migration.
Generally SQLServer shops use SS specific functions and T-SQL heavily since they provide very good functionality. For example:
1, convert function is used heavily in SQL to format various datetime formats.
2. SS does case insensitive searches. Converting it to PG involves modifying the SQL. Not an easy job to do.
3. SS has 3 part structures. DB.SCHEMA.TABLE which can be used in SQL. PG can go only up to 2 part SCHEMA.TABLE. 3 part is possible, but using FDW or other cumbersome mechanism.
Thank you. I am referring more to features, functionality, scalability, etc.
I want to get them interested in giving Postgres a try instead of SQL Server. Surely the savings on licenses can be substantial (I have no idea how much, TBH), but I want to instill confidence in them that anything they do with SQL Server can be done with Postgres.