Merge pull request #10096 from julieMSFT/JSON

Updating JSON articles to show supported in SQL DW

Author: v-shils

docs/relational-databases/json/convert-json-data-to-rows-and-columns-with-openjson-sql-server.md

@@ -15,10 +15,10 @@ author: jovanpop-msft
 ms.author: jovanpop
 ms.reviewer: genemi
 manager: craigg
-monikerRange: "=azuresqldb-current||>=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017||=azuresqldb-mi-current"
+monikerRange: "=azuresqldb-current||= azure-sqldw-latest||>=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017||=azuresqldb-mi-current"
 ---
 # Parse and Transform JSON Data with OPENJSON (SQL Server)
-[!INCLUDE[appliesto-ss-asdb-xxxx-xxx-md](../../includes/appliesto-ss-asdb-xxxx-xxx-md.md)]
+[!INCLUDE[appliesto-ss-asdb-asdw-xxx-md](../../includes/appliesto-ss-asdb-asdw-xxx-md.md)]
 
 The **OPENJSON** rowset function converts JSON text into a set of rows and columns. After you transform a JSON collection into a rowset with **OPENJSON**, you can run any SQL query on the returned data or insert it into a SQL Server table. 
 
@@ -37,9 +37,10 @@ When you use the **OPENJSON** function without providing an explicit schema for
 **OPENJSON** returns each property of the JSON object, or each element of the array, as a separate row.  
 
 Here's a quick example that uses **OPENJSON** with the default schema - that is, without the optional **WITH** clause - and returns one row for each property of the JSON object.  
- 
+
 **Example**
-```sql  
+
+```sql
 DECLARE @json NVARCHAR(MAX)
 
 SET @json='{"name":"John","surname":"Doe","age":45,"skills":["SQL","C#","MVC"]}';
@@ -48,7 +49,7 @@ SELECT *
 FROM OPENJSON(@json);
 ```  
 
-**Results**  
+**Results**
 
 |key|value|type|  
 |---------|-----------|----------|  
@@ -63,8 +64,8 @@ For more info and examples, see [Use OPENJSON with the Default Schema (SQL S
 
 For syntax and usage, see [OPENJSON (Transact-SQL)](../../t-sql/functions/openjson-transact-sql.md). 
 
-    
 ## Option 2 - OPENJSON output with an explicit structure
+
 When you specify a schema for the results by using the **WITH** clause of the **OPENJSON** function, the function returns a table with only the columns that you define in the **WITH** clause. In the optional **WITH** clause, you specify a set of output columns, their types, and the paths of the JSON source properties for each output value. **OPENJSON** iterates through the array of JSON objects, reads the value on the specified path for each column, and converts the value to the specified type.  
 
 Here's a quick example that uses **OPENJSON** with a schema for the output that you explicitly specify in the **WITH** clause.  
@@ -109,7 +110,7 @@ WITH (
  ) 
 ```  
 
-**Results**  
+**Results**
 
 |Number|Date|Customer|Quantity|  
 |------------|----------|--------------|--------------|  
@@ -123,11 +124,13 @@ This function returns and formats the elements of a JSON array.
 -   For each column, specified by using the `colName type json_path` syntax, **OPENJSON** converts the value found in each array element on the specified path to the specified type. In this example, values for the `Date` column are taken from each element on the path `$.Order.Date` and converted to datetime values.  
 
 ### More info about OPENJSON with an explicit schema
+
 For more info and examples, see [Use OPENJSON with an Explicit Schema (SQL Server)](../../relational-databases/json/use-openjson-with-an-explicit-schema-sql-server.md).
 
 For syntax and usage, see [OPENJSON (Transact-SQL)](../../t-sql/functions/openjson-transact-sql.md).
 
 ## OPENJSON requires Compatibility Level 130
+
 The **OPENJSON** function is available only under **compatibility level 130**. If your database compatibility level is lower than 130, SQL Server can't find and run the **OPENJSON** function. Other built-in JSON functions are available at all compatibility levels.
 
 You can check compatibility level in the `sys.databases` view or in database properties.
@@ -141,13 +144,12 @@ You can change the compatibility level of a database by using the following comm
 
 For a visual introduction to the built-in JSON support in SQL Server and Azure SQL Database, see the following videos:
 
--   [SQL Server 2016 and JSON Support](https://channel9.msdn.com/Shows/Data-Exposed/SQL-Server-2016-and-JSON-Support)
+- [SQL Server 2016 and JSON Support](https://channel9.msdn.com/Shows/Data-Exposed/SQL-Server-2016-and-JSON-Support)
 
--   [Using JSON in SQL Server 2016 and Azure SQL Database](https://channel9.msdn.com/Shows/Data-Exposed/Using-JSON-in-SQL-Server-2016-and-Azure-SQL-Database)
+- [Using JSON in SQL Server 2016 and Azure SQL Database](https://channel9.msdn.com/Shows/Data-Exposed/Using-JSON-in-SQL-Server-2016-and-Azure-SQL-Database)
 
--   [JSON as a bridge between NoSQL and relational worlds](https://channel9.msdn.com/events/DataDriven/SQLServer2016/JSON-as-a-bridge-betwen-NoSQL-and-relational-worlds)
+- [JSON as a bridge between NoSQL and relational worlds](https://channel9.msdn.com/events/DataDriven/SQLServer2016/JSON-as-a-bridge-betwen-NoSQL-and-relational-worlds)
 
 ## See Also  
  [OPENJSON (Transact-SQL)](../../t-sql/functions/openjson-transact-sql.md)  
-  
-  
+  

docs/relational-databases/json/json-data-sql-server.md

@@ -14,30 +14,30 @@ author: jovanpop-msft
 ms.author: jovanpop
 ms.reviewer: genemi
 manager: craigg
-monikerRange: "=azuresqldb-current||>=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017||=azuresqldb-mi-current"
+monikerRange: "=azuresqldb-current||= azure-sqldw-latest||>=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017||=azuresqldb-mi-current"
 ---
 
 # JSON data in SQL Server
-[!INCLUDE[appliesto-ss2016-asdb-xxxx-xxx-md.md](../../includes/tsql-appliesto-ss2016-asdb-xxxx-xxx-md.md)]
+[!INCLUDE[appliesto-ss2016-asdb-asdw-xxx-md.md](../../includes/tsql-appliesto-ss2016-asdb-asdw-xxx-md.md)]
 
 JSON is a popular textual data format that's used for exchanging data in modern web and mobile applications. JSON is also used for storing unstructured data in log files or NoSQL databases such as Microsoft Azure Cosmos DB. Many REST web services return results that are formatted as JSON text or accept data that's formatted as JSON. For example, most Azure services, such as Azure Search, Azure Storage, and Azure Cosmos DB, have REST endpoints that return or consume JSON. JSON is also the main format for exchanging data between webpages and web servers by using AJAX calls. 
 
 JSON functions in SQL Server enable you to combine NoSQL and relational concepts in the same database. Now you can combine classic relational columns with columns that contain documents formatted as JSON text in the same table, parse and import JSON documents in relational structures, or format relational data to JSON text. You see how JSON functions connect relational and NoSQL concepts in SQL Server and Azure SQL Database in the following video:
 
 *JSON as a bridge between NoSQL and relational worlds*
 > [!VIDEO https://channel9.msdn.com/events/DataDriven/SQLServer2016/JSON-as-a-bridge-betwen-NoSQL-and-relational-worlds/player]
- 
-Here's an example of JSON text: 
- 
-```json 
+
+Here's an example of JSON text:
+
+```json
 [{
 	"name": "John",
 	"skills": ["SQL", "C#", "Azure"]
 }, {
 	"name": "Jane",
 	"surname": "Doe"
 }]
-``` 
+```
 
 By using SQL Server built-in functions and operators, you can do the following things with JSON text: 
 
@@ -121,7 +121,7 @@ FROM OPENJSON(@json)
 
 **Results**  
 
-|id|firstName|lastName|age|dateOfBirth|  
+|ID|firstName|lastName|age|dateOfBirth|  
 |--------|---------------|--------------|---------|-----------------|  
 |2|John|Smith|25||  
 |5|Jane|Smith||2005-11-04T12:00:00|  
@@ -150,7 +150,7 @@ N'[
 
 SELECT *  
 FROM OPENJSON(@json)  
-  WITH (id int 'strict $.id',  
+  WITH id int 'strict $.id',  
         firstName nvarchar(50) '$.info.name', lastName nvarchar(50) '$.info.surname',  
         age int, dateOfBirth datetime2 '$.dob',
 	skills nvarchar(max) '$.info.skills' as json) 
@@ -162,7 +162,7 @@ The result of this query is shown in the following table:
 
 **Results**  
 
-|id|firstName|lastName|age|dateOfBirth|skill|  
+|ID|firstName|lastName|age|dateOfBirth|skill|  
 |--------|---------------|--------------|---------|-----------------|----------|  
 |2|John|Smith|25|||  
 |5|Jane|Smith||2005-11-04T12:00:00|SQL| 
@@ -172,6 +172,10 @@ The result of this query is shown in the following table:
 `OUTER APPLY OPENJSON` will join first level entity with sub-array and return flatten resultset. Due to JOIN, the second row will be repeated for every skill.
 
 ### Convert SQL Server data to JSON or export JSON
+
+>[!NOTE]
+>Converting Azure SQL Data Warehouse data to JSON or exporting JSON is not supported.
+
 Format SQL Server data or the results of SQL queries as JSON by adding the **FOR JSON** clause to a **SELECT** statement. Use **FOR JSON** to delegate the formatting of JSON output from your client applications to SQL Server. For more information, see [Format Query Results as JSON with FOR JSON (SQL Server)](../../relational-databases/json/format-query-results-as-json-with-for-json-sql-server.md).  
 
 The following example uses PATH mode with the **FOR JSON** clause:  
@@ -327,11 +331,11 @@ If you have a web service that takes data from the database layer and returns it
 
 For example, you might want to generate JSON output that's compliant with the OData specification. The web service expects a request and response in the following format: 
 
--   Request: `/Northwind/Northwind.svc/Products(1)?$select=ProductID,ProductName`  
+- Request: `/Northwind/Northwind.svc/Products(1)?$select=ProductID,ProductName`  
 
--   Response: `{"@odata.context":"https://services.odata.org/V4/Northwind/Northwind.svc/$metadata#Products(ProductID,ProductName)/$entity","ProductID":1,"ProductName":"Chai"}`  
+- Response: `{"@odata.context":"https://services.odata.org/V4/Northwind/Northwind.svc/$metadata#Products(ProductID,ProductName)/$entity","ProductID":1,"ProductName":"Chai"}`  
 
-This OData URL represents a request for the ProductID and ProductName columns for the product with `id` 1. You can use **FOR JSON** to format the output as expected in SQL Server.  
+This OData URL represents a request for the ProductID and ProductName columns for the product with `ID` 1. You can use **FOR JSON** to format the output as expected in SQL Server.  
 
 ```sql  
 SELECT 'https://services.odata.org/V4/Northwind/Northwind.svc/$metadata#Products(ProductID,ProductName)/$entity'

docs/t-sql/functions/isjson-transact-sql.md

@@ -18,9 +18,10 @@ author: "jovanpop-msft"
 ms.author: "jovanpop"
 ms.reviewer: genemi
 manager: craigg
+monikerRange: "= azuresqldb-current||= azure-sqldw-latest||>= sql-server-2016||>= sql-server-linux-2017||= sqlallproducts-allversions"
 ---
 # ISJSON (Transact-SQL)
-[!INCLUDE[tsql-appliesto-ss2016-asdb-xxxx-xxx-md](../../includes/tsql-appliesto-ss2016-asdb-xxxx-xxx-md.md)]
+[!INCLUDE[tsql-appliesto-ss2016-asdb-asdw-xxx-md](../../includes/tsql-appliesto-ss2016-asdb-asdw-xxx-md.md)]
 
   Tests whether a string contains valid JSON.  
 

docs/t-sql/functions/json-functions-transact-sql.md

@@ -14,9 +14,11 @@ author: "jovanpop-msft"
 ms.author: "jovanpop"
 ms.reviewer: genemi
 manager: craigg
+monikerRange: "= azuresqldb-current||= azure-sqldw-latest||>= sql-server-2016||>= sql-server-linux-2017||= sqlallproducts-allversions"
 ---
 # JSON Functions (Transact-SQL)
-[!INCLUDE[tsql-appliesto-ss2016-asdb-xxxx-xxx-md](../../includes/tsql-appliesto-ss2016-asdb-xxxx-xxx-md.md)]
+
+[!INCLUDE[tsql-appliesto-ss2016-asdb-asdw-xxx-md](../../includes/tsql-appliesto-ss2016-asdb-asdw-xxx-md.md)]
 
 Use the functions described on the pages in this section to validate or change JSON text or to extract simple or complex values.  
 
@@ -28,10 +30,9 @@ Use the functions described on the pages in this section to validate or change J
 |[JSON_MODIFY](../../t-sql/functions/json-modify-transact-sql.md)|Updates the value of a property in a JSON string and returns the updated JSON string.|
 
  For more info about the built-in support for JSON in [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], see [JSON Data (SQL Server)](../../relational-databases/json/json-data-sql-server.md).  
-    
-## See Also  
- [Validate, Query, and Change JSON Data with Built-in Functions (SQL Server)](../../relational-databases/json/validate-query-and-change-json-data-with-built-in-functions-sql-server.md)   
- [JSON Path Expressions (SQL Server)](../../relational-databases/json/json-path-expressions-sql-server.md)   
- [JSON Data (SQL Server)](../../relational-databases/json/json-data-sql-server.md)  
-  
-  
+
+## See Also
+
+ - [Validate, Query, and Change JSON Data with Built-in Functions (SQL Server)](../../relational-databases/json/validate-query-and-change-json-data-with-built-in-functions-sql-server.md)
+ - [JSON Path Expressions (SQL Server)](../../relational-databases/json/json-path-expressions-sql-server.md)
+ - [JSON Data (SQL Server)](../../relational-databases/json/json-data-sql-server.md)