Importing JSON Data from Web Services and Applications into SQL Server

To support many applications, it makes sense for the database to work with JSON data, because it is the built-in way for a JavaScript or TypeScript application to represent object data. It can mean less network traffic, looser coupling, and less need for the application developer to require full access to the base tables of the database. However, it means that the database must do plenty of checks first before importing. Phil Factor explains how it can be easily done.

Consuming hierarchical JSON documents in SQL Server using OpenJSON

Over the years, Phil was struck by the problems of reading and writing JSON documents with SQL Server, and wrote several articles on ways of overcoming these problems. Now that SQL Server 2016 onwards has good JSON support, he thought that the articles would be forgotten. Not so, they continue to be popular, so he felt obliged to write about how you can use SQL Server's JSON support to speed the process up.

Representing a simple hierarchical list in SQL Server with JSON, YAML, XML and HTML

How difficult can it be to produce a simple hierarchical list in JSON, YAML, XML and HTML from a SQL Server table that represents a simple hierarchy within an organisation. Well once you know, it is easy and William Brewer is on a mission to tell you how.

JSON query issues

SQL Server 2016: built-in JSON Use case scenarios

There's built-in JSON support starting with SQL Server 2016. Does that mean we should all ditch XML and start using JSON? It depends mostly on the target of your data output processing.

JSON Path Mode

JSON Paths

Default OPENJSON

ISJSON

Consuming JSON Formatted API Data in 2016

Natively consume JSON data from API sources with SQL 2016 and CLR