My daughter explores every new toy, and that is how I play with JSON in SQL Server 2016. One surprise: JSON paths are case-sensitive, as this example shows.
SQL SERVER – Fix Error Msg 13603 working with JSON documents
Msg 13603 appeared when I used a custom path with FOR JSON PATH, because the column alias had an invalid character. Here is how to fix it.
Calling a REST API From T-SQL With sp_invoke_external_rest_endpoint
Use sp_invoke_external_rest_endpoint in SQL Server 2025 with controlled permissions, JSON responses, protected credentials, and retries.
SQL SERVER – Fix Error Msg 13602 working with JSON documents
Working with JSON documents in SQL Server 2016? You can’t use FOR JSON inside an UPDATE statement, and trying gives Msg 13602. Here is how to work around it.
SQL SERVER – Error Fix: Msg 13601 Working with JSON Structure
Msg 13601 showed up while I was working with JSON output: a property cannot be generated due to a conflict with another column name. Here is the fix.
SQL SERVER – 2016 – Check Value as JSON With ISJSON()
Before you store JSON sent from the front end, make sure it is valid. Here is how the ISJSON() function in SQL Server 2016 checks a value as JSON.
SQL SERVER – 2016 – Opening JSON with OPENJSON()
The next step with JSON in SQL Server 2016 is reading it. OPENJSON parses JSON text and returns properties as rows. A simple example with the default schema.