We are approaching the most interesting part of these article series. I have mentioned that developers give preferences to JSON as it has clear structure and smaller data size comparing to XML.
In this article, we are going to compare JSON vs XML performance.
In this article, we will explore how we can store and index JSON objects in a database.
As we have already discussed, developers did not add a separate type for JSON to SQL Server 2016 as they did for XML.
In my previous article, we have explored how we can transform JSON into the relational data set. We have already analyzed main steps of working with JSON. Now, I am going to describe how you can modify JSON files built into SQL Server.
In my previous publication, I described how you could generate JSON from relational data. In this article, we will explore the reverse operation: how it is possible to transform JSON into a relational structure. To do this, you can use the OPENJSON statement.
In my previous publication, we have explored how you can transfer data from JSON to SQL Server 2016. Now, I am going to describe how you can generate JSON from relational data. You can do this using the FOR JSON statement.
JSON is one of the most widely used data interchange formats. It is used as a storing format in several NoSQL solutions, in particular, in Microsoft Azure DocumentDB. In my opinion, today JSON is yet more popular than XML. One of the reasons of its popularity is more simple form and better readability in comparison with XML. Naturally, there was a long-standing need in having an option to process data in this format within SQL Server. In SQL Server 2016, this option has been established. Read More