> Next to Azure, this is the next biggest cause of issues at work for me, and I haven't seen any wild advantage of this over Postgres, with the disadvantage that pretty much every linux/macOS and open source tool I use is much happier to plug in to Postgres instead.
It's been a pretty great thing for me, if only to be able to get a better local experience with Docker. A lot of our applications are centered around MSSQL Server (for better or worse), I'll say that despite the costs, replication in MS SQL is night and day better than Postgres.
It really depends on how you use SQL Server because it doesn't support all the features of the Windows version and if software uses those features, it gets pretty ugly. That said, if you develop against the Linux version, you're unlikely to have issues deploying to the full version, or Azure SQL.
Of course on other projects we're using PostgreSQL and I tend to prefer it as binary json support is huge imo. Getting other devs to understand that you don't need to break off child records into separate tables that require series of joins, that's another story.
> Next to Azure, this is the next biggest cause of issues at work for me, and I haven't seen any wild advantage of this over Postgres, with the disadvantage that pretty much every linux/macOS and open source tool I use is much happier to plug in to Postgres instead.
It's been a pretty great thing for me, if only to be able to get a better local experience with Docker. A lot of our applications are centered around MSSQL Server (for better or worse), I'll say that despite the costs, replication in MS SQL is night and day better than Postgres.
It really depends on how you use SQL Server because it doesn't support all the features of the Windows version and if software uses those features, it gets pretty ugly. That said, if you develop against the Linux version, you're unlikely to have issues deploying to the full version, or Azure SQL.
Of course on other projects we're using PostgreSQL and I tend to prefer it as binary json support is huge imo. Getting other devs to understand that you don't need to break off child records into separate tables that require series of joins, that's another story.