Merge pull request #31554 from MashaMSFT/202408_sqlmijson

prmerger-automator[bot] · web-flow · commit f2fe6963ed8a · 2024-08-20T15:27:40.000Z
added sql mi json support
diff --git a/azure-sql/managed-instance/doc-changes-updates-release-notes-whats-new.md b/azure-sql/managed-instance/doc-changes-updates-release-notes-whats-new.md
@@ -5,7 +5,7 @@ description: Learn about the new features and documentation improvements for Azu
 author: MashaMSFT
 ms.author: mathoma
 ms.reviewer: wiassaf, mathoma
-ms.date: 08/13/2024
+ms.date: 08/20/2024
 ms.service: azure-sql-managed-instance
 ms.subservice: service-overview
 ms.topic: whats-new
@@ -40,6 +40,8 @@ The following table lists the features of Azure SQL Managed Instance that are cu
 |[Fail over a link with T-SQL](managed-instance-link-failover-how-to.md?tabs=tsql#fail-over-a-database) | You can now fail over a [managed instance link](managed-instance-link-feature-overview.md) by using Transact-SQL (T-SQL) commands. |
 |[Free SQL Managed Instance](free-offer.md) | Try Azure SQL Managed Instance for free, for the first 12 months after you create your instance. |
 |[Instance pools](instance-pools-overview.md) | Share resources between multiple instances in a pool within a single virtual machine. A convenient and cost-efficient way to migrate smaller SQL Server instances to the cloud, and the only way to deploy a 2-vCore managed instance. |
+|[JSON native data type](/sql/t-sql/data-types/json-data-type) | The new **JSON** native data type is currently in preview. For more information, see [JSON Type and aggregates preview](https://aka.ms/json-type-aggregates-public-preview). Your SQL managed instance must be configured with the [Always-up-to-date update policy](update-policy.md#always-up-to-date-update-policy).|
+|[JSON aggregate functions](/sql/relational-databases/json/json-data-sql-server#json-data-from-aggregates) | Two new **JSON** aggregate functions `JSON_OBJECTAGG` and `JSON_ARRAYAGG` enable construction of JSON objects or arrays based on an aggregate from SQL data. Your SQL managed instance must be configured with the [Always-up-to-date update policy](update-policy.md#always-up-to-date-update-policy). For more information, see [JSON Type and aggregates preview](https://aka.ms/json-type-aggregates-public-preview). |
 |[Link from SQL MI to SQL Server](managed-instance-link-feature-overview.md) | Configure a link *from* Azure SQL Managed Instance to SQL Server 2022. |
 |[Microsoft Entra nonunique name support](../database/authentication-microsoft-entra-create-users-with-nonunique-names.md) |  The [CREATE USER](/sql/t-sql/statements/create-user-transact-sql) Transact-SQL (T-SQL) syntax has been extended to include `WITH OBJECT_ID` to support creating Microsoft Entra logins and users in Azure SQL Managed Instance that have nonunique names. |
 |[Native Windows principals](native-windows-principals.md) | Use the new **Windows** authentication metadata mode to allow Windows authentication or Microsoft Entra authentication (using a Windows principal metadata) with Azure SQL Managed Instance. |
@@ -105,6 +107,8 @@ Learn about significant changes to the Azure SQL Managed Instance documentation.
 
 | Changes | Details |
 | --- | --- |
+| **JSON native data type preview** | The new [**JSON** native data type](/sql/t-sql/data-types/json-data-type) and is currently in preview. For more information, see [JSON Type and aggregates preview](https://aka.ms/json-type-aggregates-public-preview). Your SQL managed instance must be configured with the [Always-up-to-date update policy](update-policy.md#always-up-to-date-update-policy).|
+| **JSON aggregate functions preview** | Two new **JSON** aggregate functions [JSON_OBJECTAGG and JSON_ARRAYAGG](/sql/relational-databases/json/json-data-sql-server#json-data-from-aggregates) enable construction of JSON objects or arrays based on an aggregate from SQL data. For more information, see [JSON Type and aggregates preview](https://aka.ms/json-type-aggregates-public-preview). Your SQL managed instance must be configured with the [the Always-up-to-date update policy](update-policy.md#always-up-to-date-update-policy).|
 | **Fail over link with T-SQL preview** | You can now fail over a [managed instance link](managed-instance-link-feature-overview.md) by using Transact-SQL (T-SQL) commands. This capability is currently in preview starting with [SQL Server 2022 CU13 (KB5036432)](/troubleshoot/sql/releases/sqlserver-2022/cumulativeupdate13). To learn more, review [fail over a database](managed-instance-link-failover-how-to.md?tabs=tsql#fail-over-a-database). |
 
 ### July 2024
diff --git a/azure-sql/managed-instance/update-policy.md b/azure-sql/managed-instance/update-policy.md
@@ -5,7 +5,7 @@ description: Use the update policy setting in Azure SQL Managed Instance to cont
 author: MladjoA
 ms.author: mlandzic
 ms.reviewer: mathoma
-ms.date: 05/22/2024
+ms.date: 08/20/2024
 ms.service: azure-sql-managed-instance
 ms.subservice: deployment-configuration
 ms.topic: how-to
@@ -57,9 +57,9 @@ When using the **Always-up-to-date** update policy, consider the following:
 The following table lists all the features that are only available to instances with the designated update policy:
 
 
-|**SQL Server 2022** update policy  |**Always-up-to-date** update policy  |
+|SQL Server 2022 update policy  |Always-up-to-date update policy  |
 |---------|---------|
-|[Restore database to SQL Server 2022](restore-database-to-sql-server.md)  <br /> [Link with bidirectional failover and disaster recovery](managed-instance-link-disaster-recovery.md)   | While currently, there aren't any features that are only available to instances with the **Always-up-to-date** update policy, check back soon. |
+|- [Restore database to SQL Server 2022](restore-database-to-sql-server.md)  <br /> - [Link with bidirectional failover and disaster recovery](managed-instance-link-disaster-recovery.md)   | [JSON data type](/sql/t-sql/data-types/json-data-type) |
 
 
 The following features are impacted by the configured update policy: 
diff --git a/docs/relational-databases/json/index-json-data.md b/docs/relational-databases/json/index-json-data.md
@@ -4,7 +4,7 @@ description: "Index JSON data"
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: jroth, jovanpop
-ms.date: 05/21/2024
+ms.date: 08/20/2024
 ms.service: sql
 ms.custom:
   - build-2024
@@ -20,7 +20,7 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||
 You can optimize your queries over JSON documents using standard indexes. SQL Server does not have custom JSON indexes.
 
 - Currently, in SQL Server **json** is not a built-in data type.
-- Currently, the [JSON data type](../../t-sql/data-types/json-data-type.md) is available in Azure SQL Database.
+- The [JSON data type](../../t-sql/data-types/json-data-type.md) is currently in preview for Azure SQL Database and Azure SQL Managed Instance (configured with the [**Always-up-to-date** update policy](/azure/azure-sql/managed-instance/update-policy#always-up-to-date-update-policy)). 
 
 Indexes work the same way on JSON data in **varchar**/**nvarchar** or the [native **json** data type](../../t-sql/data-types/json-data-type.md).
 
diff --git a/docs/relational-databases/json/json-data-sql-server.md b/docs/relational-databases/json/json-data-sql-server.md
@@ -4,7 +4,7 @@ description: Combine NoSQL and relational concepts in the same database with JSO
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: randolphwest, jovanpop
-ms.date: 05/21/2024
+ms.date: 08/20/2024
 ms.service: sql
 ms.topic: quickstart
 ms.custom:
@@ -64,7 +64,7 @@ The new **json** data type that stores JSON documents in a native binary format
 - No change in compatibility with existing code
 
 > [!NOTE]
-> - Currently, the [JSON data type](../../t-sql/data-types/json-data-type.md) is available in Azure SQL Database.
+> The [JSON data type](../../t-sql/data-types/json-data-type.md) is currently in preview for Azure SQL Database and Azure SQL Managed Instance (configured with the [**Always-up-to-date** update policy](/azure/azure-sql/managed-instance/update-policy#always-up-to-date-update-policy)). 
 
 Using the JSON same functions described in this article remain the most efficient way to query the **json** data type. For more information on the native **json** data type, see [JSON data type](../../t-sql/data-types/json-data-type.md).
 
@@ -256,7 +256,7 @@ JSON aggregate functions enable construction of JSON objects or arrays based on
 - [JSON_ARRAYAGG](../../t-sql/functions/json-arrayagg-transact-sql.md) constructs a JSON **array** from an aggregation of SQL data or columns.
 
 > [!NOTE]
-> Currently, both **json** aggregate functions `JSON_OBJECTAGG` and `JSON_ARRAYAGG` are available in preview for Azure SQL Database.
+> Both **json** aggregate functions `JSON_OBJECTAGG` and `JSON_ARRAYAGG` are currently in preview for Azure SQL Database and Azure SQL Managed Instance (configured with the [**Always-up-to-date** update policy](/azure/azure-sql/managed-instance/update-policy#always-up-to-date-update-policy)). 
 
 ## Use cases for JSON data in SQL Server
 
diff --git a/docs/relational-databases/json/store-json-documents-in-sql-tables.md b/docs/relational-databases/json/store-json-documents-in-sql-tables.md
@@ -4,7 +4,7 @@ description: "Learn why and how to store and index JSON documents, and how to op
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: umajay 
-ms.date: 08/01/2024
+ms.date: 08/20/2024
 ms.service: sql
 ms.custom:
   - build-2024
@@ -22,7 +22,7 @@ The first storage design decision is how to store JSON documents in the tables.
 - **LOB storage** - JSON documents can be stored as-is in columns with the data type **json** or **nvarchar**. This is the best way for quick data load and ingestion because the loading speed matches the loading speed of string columns. This approach might introduce an additional performance penalty on query/analysis time if indexing on JSON values is not performed, because the raw JSON documents must be parsed while the queries are running. 
 - **Relational storage** - JSON documents can be parsed while they are inserted in the table using `OPENJSON`, `JSON_VALUE` or `JSON_QUERY` functions. Fragments from the input JSON documents can be stored in the columns containing JSON sub-elements with data types **json** or **nvarchar**. This approach increases the load time because JSON parsing is done during load; however, queries match the performance of classic queries on the relational data.
 
-- Currently, the [JSON data type](../../t-sql/data-types/json-data-type.md) is available in Azure SQL Database.
+- The [JSON data type](../../t-sql/data-types/json-data-type.md) is currently in preview for Azure SQL Database and Azure SQL Managed Instance (configured with the [**Always-up-to-date** update policy](/azure/azure-sql/managed-instance/update-policy#always-up-to-date-update-policy)). 
 - Currently in SQL Server, JSON is not a built-in data type.
 
 ## Classic tables
diff --git a/docs/t-sql/data-types/json-data-type.md b/docs/t-sql/data-types/json-data-type.md
@@ -4,19 +4,19 @@ description: The native JSON data type provides advantages for storing JSON data
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: randolphwest, jovanpop
-ms.date: 05/21/2024
+ms.date: 08/20/2024
 ms.service: sql
 ms.topic: quickstart
 ms.custom:
   - intro-quickstart
   - build-2024
 helpviewer_keywords:
   - "JSON data type"
-monikerRange: "=azuresqldb-current"
+monikerRange: "=azuresqldb-current || =azuresqldb-mi-current"
 ---
 # JSON data type (preview)
 
-[!INCLUDE [asdb](../../includes/applies-to-version/asdb.md)]
+[!INCLUDE [asdb](../../includes/applies-to-version/asdb-asdbmi.md)]
 
 The new native **json** data type that stores JSON documents in a native binary format.
 
@@ -60,7 +60,7 @@ JSON support was first introduced in [!INCLUDE [sssql16-md](../../includes/sssql
 **json** is available under all database compatibility levels.
 
 > [!NOTE]  
-> Currently, the **json** type is available in preview on Azure SQL Database.
+> The [JSON data type](../../t-sql/data-types/json-data-type.md) is currently in preview for Azure SQL Database and Azure SQL Managed Instance (configured with the [**Always-up-to-date** update policy](/azure/azure-sql/managed-instance/update-policy#always-up-to-date-update-policy)). 
 
 ## Function support
 
diff --git a/docs/t-sql/functions/json-arrayagg-transact-sql.md b/docs/t-sql/functions/json-arrayagg-transact-sql.md
@@ -4,7 +4,7 @@ description: JSON_ARRAYAGG constructs a JSON array from an aggregation of SQL da
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: umajay
-ms.date: 05/21/2024
+ms.date: 08/20/2024
 ms.service: sql
 ms.subservice: t-sql
 ms.topic: reference
@@ -17,18 +17,18 @@ dev_langs:
   - "TSQL"
 ms.custom:
   - build-2024
-monikerRange: "=azuresqldb-current"
+monikerRange: "=azuresqldb-current || =azuresqldb-mi-current"
 ---
 # JSON_ARRAYAGG (Transact-SQL)
 
-[!INCLUDE [asdb](../../includes/applies-to-version/asdb.md)]
+[!INCLUDE [asdb](../../includes/applies-to-version/asdb-asdbmi.md)]
 
  Constructs a JSON array from an aggregation of SQL data or columns.
 
  To create a JSON object from an aggregate instead, use [JSON_OBJECTAGG](json-objectagg-transact-sql.md).
   
 > [!NOTE]
-> Currently, both **json** aggregate functions `JSON_OBJECTAGG` and `JSON_ARRAYAGG` are available in preview for Azure SQL Database. 
+> Both **json** aggregate functions `JSON_OBJECTAGG` and `JSON_ARRAYAGG` are currently in preview for Azure SQL Database and Azure SQL Managed Instance (configured with the [**Always-up-to-date** update policy](/azure/azure-sql/managed-instance/update-policy#always-up-to-date-update-policy)). . 
 
  :::image type="icon" source="../../includes/media/topic-link-icon.svg" border="false"::: [Transact-SQL syntax conventions](../../t-sql/language-elements/transact-sql-syntax-conventions-transact-sql.md)  
   
diff --git a/docs/t-sql/functions/json-functions-transact-sql.md b/docs/t-sql/functions/json-functions-transact-sql.md
@@ -4,7 +4,7 @@ description: Use JSON functions to validate or change JSON text, or to extract s
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: jovanpop, randolphwest
-ms.date: 05/15/2024
+ms.date: 08/20/2024
 ms.service: sql
 ms.subservice: t-sql
 ms.topic: reference
diff --git a/docs/t-sql/functions/json-objectagg-transact-sql.md b/docs/t-sql/functions/json-objectagg-transact-sql.md
@@ -4,7 +4,7 @@ description: JSON_OBJECTAGG constructs a JSON object from an aggregation of SQL
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: umajay
-ms.date: 05/21/2024
+ms.date: 08/20/2024
 ms.service: sql
 ms.subservice: t-sql
 ms.topic: reference
@@ -17,11 +17,11 @@ dev_langs:
   - "TSQL"
 ms.custom:
   - build-2024
-monikerRange: "=azuresqldb-current"
+monikerRange: "=azuresqldb-current || =azuresqldb-mi-current"
 ---
 # JSON_OBJECTAGG (Transact-SQL)
 
-[!INCLUDE [asdb](../../includes/applies-to-version/asdb.md)]
+[!INCLUDE [asdb](../../includes/applies-to-version/asdb-asdbmi.md)]
 
  Constructs a JSON object from an aggregation of SQL data or columns.
   
@@ -30,7 +30,7 @@ monikerRange: "=azuresqldb-current"
  To create a JSON array from an aggregate instead, use [JSON_ARRAYAGG](json-arrayagg-transact-sql.md).
 
 > [!NOTE]
-> Currently, both **json** aggregate functions `JSON_OBJECTAGG` and `JSON_ARRAYAGG` are available in preview for Azure SQL Database.
+> Both **json** aggregate functions `JSON_OBJECTAGG` and `JSON_ARRAYAGG` are currently in preview for Azure SQL Database and Azure SQL Managed Instance (configured with the [**Always-up-to-date** update policy](/azure/azure-sql/managed-instance/update-policy#always-up-to-date-update-policy)).
 
  :::image type="icon" source="../../includes/media/topic-link-icon.svg" border="false"::: [Transact-SQL syntax conventions](../../t-sql/language-elements/transact-sql-syntax-conventions-transact-sql.md)  
   
