Merge pull request #32914 from MicrosoftDocs/main

Albertyang0 · web-flow · commit d656648b736a · 2025-01-22T15:30:16.000-08:00
1/22/2025 PM Publish
diff --git a/docs/includes/applies-to-version/sql-asdb-asdbmi-asa-dedicated-poolonly-fabricse-fabricdw.md b/docs/includes/applies-to-version/sql-asdb-asdbmi-asa-dedicated-poolonly-fabricse-fabricdw.md
@@ -0,0 +1,9 @@
+---
+author: WilliamDAssafMSFT
+ms.author: wiassaf
+ms.date: 01/22/2025
+ms.service: sql
+ms.topic: include
+---
+
+[!INCLUDE [Applies to](../../includes/applies-md.md)] [!INCLUDE [SQL Server](_ssnoversion.md)] [!INCLUDE [Azure SQL Database](../../includes/applies-to-version/_asdb.md)] [!INCLUDE [SQL Managed Instance](../../includes/applies-to-version/_asmi.md)] [!INCLUDE [Azure Synapse Analytics (dedicated SQL pool only)](../../includes/applies-to-version/_asa-sqlpool-only.md)]  [!INCLUDE [Fabric SQL analytics endpoint](../../includes/applies-to-version/_fabric-se.md)] [!INCLUDE [Fabric Data Warehouse](../../includes/applies-to-version/_fabric-dw.md)]
diff --git a/docs/linux/quickstart-install-connect-red-hat.md b/docs/linux/quickstart-install-connect-red-hat.md
@@ -37,13 +37,14 @@ For more information on supported platforms, see [Release notes for SQL Server 2
 
 In this quickstart, you install [!INCLUDE [sssql22-md](../includes/sssql22-md.md)] on Red Hat Enterprise Linux (RHEL) 8.x or 9.x. Then you can connect with **sqlcmd** to create your first database and run queries.
 
+If you would like to automate your installation using Ansible, see [Quickstart: Deploy SQL Server on Linux using an Ansible playbook](sql-server-linux-deploy-ansible.md).
+
 For more information on supported platforms, see [Release notes for SQL Server 2022 on Linux](sql-server-linux-release-notes-2022.md).
 
 ::: moniker-end
 
 > [!TIP]  
-> This tutorial requires user input and an internet connection. If you're interested in the [unattended](sql-server-linux-setup.md#unattended) or [offline](sql-server-linux-setup.md#offline) installation procedures, see [Installation guidance for SQL Server on Linux](sql-server-linux-setup.md).
-If you choose to have a pre-installed [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)] VM on RHEL ready to run your production-based workload, follow the [best practices](/azure/azure-sql/virtual-machines/windows/performance-guidelines-best-practices-checklist) for creating the SQL Server VM.
+> This tutorial requires user input and an internet connection. If you're interested in the [unattended](sql-server-linux-setup.md#unattended) or [offline](sql-server-linux-setup.md#offline) installation procedures, see [Installation guidance for SQL Server on Linux](sql-server-linux-setup.md). If you choose to have a preinstalled [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)] VM on RHEL ready to run your production-based workload, follow the [best practices](/azure/azure-sql/virtual-machines/windows/performance-guidelines-best-practices-checklist) for creating the SQL Server VM.
 
 <!--SQL Server 2019 on Linux-->
 ::: moniker range="=sql-server-linux-ver15 || =sql-server-ver15"
@@ -74,6 +75,8 @@ If you've previously installed a Community Technology Preview (CTP) or Release C
 
 For other system requirements, see [System requirements for SQL Server on Linux](sql-server-linux-setup.md#system).
 
+To ensure you configure your [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)] instance according to the recommended standards, see [Performance best practices and configuration guidelines for SQL Server on Linux](sql-server-linux-performance-best-practices.md).
+
 <a id="install"></a>
 
 ## Install SQL Server
diff --git a/docs/relational-databases/security/encryption/always-encrypted-wizard-ssms-21.md b/docs/relational-databases/security/encryption/always-encrypted-wizard-ssms-21.md
@@ -4,7 +4,7 @@ description: Learn how to configure Always Encrypted for database columns by usi
 author: pietervanhove
 ms.author: pivanho
 ms.reviewer: vanto, maghan, randolphwest
-ms.date: 11/12/2024
+ms.date: 01/22/2025
 ms.service: sql
 ms.subservice: security
 ms.topic: concept-article
@@ -52,9 +52,9 @@ To perform cryptographic operations using the wizard, you must have the `VIEW AN
 
 You can launch the wizard at three different levels:
 
-- You can encrypt multiple columns in different tables at a database level.
-- At a table level, if you want ypt multiple columns in the same table.
-- At a column level, if you want ypt one specific column.
+- At a database level, if you want to encrypt multiple columns in different tables.
+- At a table level, if you want to encrypt multiple columns in the same table.
+- At a column level, if you want to encrypt one specific column.
 
 1. Connect to your [!INCLUDE [ssNoVersion](../../../includes/ssnoversion-md.md)] with the Object Explorer component of [!INCLUDE [ssManStudioFull](../../../includes/ssmanstudiofull-md.md)].
 
@@ -99,17 +99,37 @@ When configuring a new column master key, you can either pick an existing key in
 
 To use in-place encryption, select **Allow enclave computations** for a new column master key. Selecting this checkbox is allowed only if your database is configured with a secure enclave.
 
-For more information about creating and storing column master keys in Windows Certificate Store, Azure Key Vault or other key stores, see [Create and store column master keys for Always Encrypted](../../../relational-databases/security/encryption/create-and-store-column-master-keys-always-encrypted.md) or [Manage keys for Always Encrypted with secure enclaves](../../../relational-databases/security/encryption/always-encrypted-enclaves-manage-keys.md).
+For more information about creating and storing column master keys in Windows Certificate Store, Azure Key Vault, or other key stores, see [Create and store column master keys for Always Encrypted](../../../relational-databases/security/encryption/create-and-store-column-master-keys-always-encrypted.md) or [Manage keys for Always Encrypted with secure enclaves](../../../relational-databases/security/encryption/always-encrypted-enclaves-manage-keys.md).
 
 > [!TIP]  
-> The wizard allows you to browse and create keys only in the Windows Certificate Store and Azure Key Vault. It also auto-generates the names of the new keys and the database metadata objects describing them. Suppose you need more control over how your keys are provisioned (and more choices for a key store containing your column master key). In that case, you can use the **New Column Master Key** and **New Column Encryption Key** dialogs to create the keys first, and then run the wizard and pick the keys you have created. See [Provision Column Master Keys with the New Column Master Key Dialog](configure-always-encrypted-keys-using-ssms.md#provision-column-master-keys-with-the-new-column-master-key-dialog) or [Provision enclave-enabled keys](always-encrypted-enclaves-provision-keys.md) and [Provision Column Encryption Keys with the New Column Encryption Key Dialog](configure-always-encrypted-keys-using-ssms.md#provision-column-encryption-keys-with-the-new-column-encryption-key-dialog).
+> The wizard allows you to browse and create keys only in the Windows Certificate Store and Azure Key Vault. It also autogenerates the names of the new keys and the database metadata objects describing them. Suppose you need more control over how your keys are provisioned (and more choices for a key store containing your column master key). In that case, you can use the **New Column Master Key** and **New Column Encryption Key** dialogs to create the keys first, and then run the wizard and pick the keys you have created. See [Provision Column Master Keys with the New Column Master Key Dialog](configure-always-encrypted-keys-using-ssms.md#provision-column-master-keys-with-the-new-column-master-key-dialog) or [Provision enclave-enabled keys](always-encrypted-enclaves-provision-keys.md) and [Provision Column Encryption Keys with the New Column Encryption Key Dialog](configure-always-encrypted-keys-using-ssms.md#provision-column-encryption-keys-with-the-new-column-encryption-key-dialog).
 
 ## In-Place Encryption Settings page
 
 If you have configured a secure enclave in your database and you're using enclave-enabled keys, this page allows you to specify the enclave attestation parameters required for in-place encryption. If you don't want to use in-place encryption, unselect **Use in-place encryption for eligible columns** to proceed with client-side encryption. We recommend leaving this checkbox enabled so that the wizard can use in-place encryption.
 
 For more information about enclave attestation, see [Configure attestation for Always Encrypted using Azure Attestation](/azure/azure-sql/database/always-encrypted-enclaves-configure-attestation)
 
+## Run Settings page
+
+The wizard supports two approaches for setting up the target encryption configuration: online and offline.
+
+With the offline approach, the target tables and any tables related to the target tables (for example, any tables a target table have foreign key relationships with) are unavailable to write transactions throughout the duration of the operation. The semantics of foreign key constraints (CHECK or NOCHECK) are always preserved when using the offline approach.
+
+With the online approach, the operation of copying, encrypting, decrypting, or re-encrypting the data is performed incrementally. Applications can read and write data from and to the target tables throughout the data movement operation, except the last iteration, the duration of which is limited by the *Maximum downtime* parameter. To detect and process the changes applications can make while the data is being copied, the wizard enables Change Tracking in the target database. Because of that, the online approach is likely to consume more resources on the database side than the offline approach. The operation might also take more time with the online approach, especially if a write-heavy workload is running against the database. The online approach can be used to encrypt **one table at a time** and the table must have a primary key. By default, foreign key constraints are recreated with the NOCHECK option to minimize the impact on applications. You can enforce preserving the semantics of foreign key constraints by enabling the `Keep check foreign key constraints` option.
+
+Here are the guidelines for choosing between the offline and online approaches:
+
+Use the offline approach:
+
+- To minimize the duration of the operation.
+- To encrypt/decrypt/re-encrypt columns in multiple tables at the same time.
+- If the target table doesn't have a primary key.
+
+Use the online approach:
+
+- To minimize the downtime/unavailability of the database to your applications.
+
 ## Related content
 
 - [Always Encrypted](../../../relational-databases/security/encryption/always-encrypted-database-engine.md)
diff --git a/docs/relational-databases/security/networking/tds-8.md b/docs/relational-databases/security/networking/tds-8.md
@@ -73,6 +73,7 @@ The following features or tools still use previous version of drivers that don't
 - Database Mail
 - Linked Servers
 - Polybase connector to SQL Server
+- SQL VSS Writer
 
 ## Additional changes to connection string encryption properties
 
diff --git a/docs/t-sql/data-types/json-data-type.md b/docs/t-sql/data-types/json-data-type.md
@@ -4,7 +4,7 @@ description: The native JSON data type provides advantages for storing JSON data
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: randolphwest, jovanpop
-ms.date: 01/07/2025
+ms.date: 01/22/2025
 ms.service: sql
 ms.topic: reference
 ms.custom:
@@ -54,7 +54,7 @@ CREATE TABLE Orders (order_id int, order_details JSON NOT NULL
 
 ## Feature availability
 
-JSON support was first introduced in [!INCLUDE [sssql16-md](../../includes/sssql16-md.md)], mostly in the form of JSON functions. The new native **json** type was introduced in 2024, first on Azure SQL platforms.
+JSON function support was first introduced in [!INCLUDE [sssql16-md](../../includes/sssql16-md.md)]. The native **json** type was introduced in 2024 in Azure SQL Database and Azure SQL Managed Instance.
 
 **json** is available under all database compatibility levels.
 
diff --git a/docs/t-sql/statements/set-showplan-xml-transact-sql.md b/docs/t-sql/statements/set-showplan-xml-transact-sql.md
@@ -3,7 +3,7 @@ title: "SET SHOWPLAN_XML (Transact-SQL)"
 description: SET SHOWPLAN_XML returns detailed information about how the statements are going to be executed in the form of a well-defined XML document.
 author: WilliamDAssafMSFT
 ms.author: wiassaf
-ms.date: 03/01/2023
+ms.date: 01/22/2025
 ms.service: sql
 ms.subservice: t-sql
 ms.topic: reference
@@ -20,14 +20,16 @@ helpviewer_keywords:
   - "estimated execution information [SQL Server]"
 dev_langs:
   - "TSQL"
-monikerRange: "=azuresqldb-current||=azure-sqldw-latest||>=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-mi-current"
+monikerRange: "=azuresqldb-current||=azure-sqldw-latest||>=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-mi-current||=fabric"
 ---
 # SET SHOWPLAN_XML (Transact-SQL)
 
-[!INCLUDE [SQL Server Azure SQL Database Azure SQL Managed Instance Synapse dedicated only](../../includes/applies-to-version/sql-asdb-asdbmi-asa-dedicated-poolonly.md)]
+[!INCLUDE [SQL Server Azure SQL Database Azure SQL Managed Instance Synapse dedicated only](../../includes/applies-to-version/sql-asdb-asdbmi-asa-dedicated-poolonly-fabricse-fabricdw.md)]
 
 Causes [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] not to execute [!INCLUDE[tsql](../../includes/tsql-md.md)] statements. Instead, [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] returns detailed information about how the statements are going to be executed in the form of a well-defined XML document.
 
+In Fabric Data Warehouse and SQL analytics endpoint, SET SHOWPLAN_XML is a preview feature.
+
 :::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)
 
 ## Syntax
@@ -105,4 +107,4 @@ SET SHOWPLAN_XML OFF;
 ## Next steps
 
 - [SET Statements (Transact-SQL)](../../t-sql/statements/set-statements-transact-sql.md)
-- [Display the Estimated Execution Plan](../../relational-databases/performance/display-the-estimated-execution-plan.md)
+- [Display the Estimated Execution Plan](../../relational-databases/performance/display-the-estimated-execution-plan.md)
