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.
OPENJSON WITH Clause: Converting JSON Properties to Typed Values
Without WITH, OPENJSON hands you text. With it, you pick the names and types and decide what happens when a property is missing.
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.
SQL SERVER – Getting Started and Creating JSON Using SQL Server 2016 – JavaScript Object Notation
SQL Server 2016 adds JSON support. Here is a quick look at what JSON (JavaScript Object Notation) is and how to create your first JSON document with a query.
JSON_CONTAINS in SQL Server 2025: Searching Inside JSON Arrays
JSON_CONTAINS checks whether a JSON document holds a value at a path, including inside an array. This post tests it on SQL Server 2025: the json data type it needs, numbers versus text, case, NULL results and the older OPENJSON way.
JSON or Real Columns: Deciding Where Attributes Live
Putting everything in a JSON column is tempting. Here is what it costs in reads, type checks and null handling, and when to promote a property.