3 ms·
> It still doesn't have proper upsert or JSON columns Upsert (MERGE) was added in SQL Server 2008 (although it's chock full of known bugs): https://www.mssqlti
by BrentOzar 8y ago
> It still doesn't have proper upsert or JSON columns
Upsert (MERGE) was added in SQL Server 2008 (although it's chock full of known bugs): https://www.mssqltips.com/sqlservertip/3074/use-caution-with-sql-servers-merge-statement/ https://www.mssqltips.com/sqlservertip/3074/use-caution-with...
JSON was added in SQL Server 2016, although indexing it is still tricky: https://docs.microsoft.com/en-us/sql/relational-databases/json/store-json-documents-in-sql-tables?view=sql-server-2017 https://docs.microsoft.com/en-us/sql/relational-databases/js...
- manigandham 8y agoThat's what I meant by "proper". It can do it, but PG does it better. It's one area that I wish they would invest time into considering the large developer impact it would have.
- SigmundA 8y agoMy understanding is they got burned by all the work put into the XML datatype and don't want to repeat it with JSON, hence the more conservative approach.