Edit one value inside a JSON document without string surgery. A hands-on tour of the quirks with types, NULL, missing paths and retries.
SQL SERVER – Understanding JSON NULL Value Using STRICT Keyword
Why does a JSON path that doesn’t match return NULL? Add the STRICT keyword to get an error instead. A follow-up on JSON NULL values in SQL Server 2016.
SQL SERVER – Understanding JSON Use is Case-Sensitive
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.
FOR JSON Data Types: How bit, Dates and Money Come Out
Your API returns 1 and the client wanted true. Here is how FOR JSON picks a JSON type for bit, dates, decimal, money, binary and NULL, and how to fix it.
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.