Merge pull request #36181 from MicrosoftDocs/main

Auto Publish – main to live - 2026-01-07 18:30 UTC

Author: learn-build-service-prod[bot]

.openpublishing.redirection.json

@@ -67205,6 +67205,11 @@
       "redirect_url": "/sql/linux/sql-server-linux-availability-group-cluster-pacemaker",
       "redirect_document_id": false
     },
+    {
+      "source_path": "docs/linux/sql-server-linux-availability-group-configure-ha.md",
+      "redirect_url": "/sql/linux/high-availability/availability-groups-configure",
+      "redirect_document_id": false
+    },
     {
       "source_path": "docs/relational-databases/system-tables/cdc-change-feed-tables-transact-sql.md",
       "redirect_url": "/sql/relational-databases/system-tables/changefeed-change-feed-tables-transact-sql",

azure-sql/includes/tls-deprecation.md

@@ -32,19 +32,19 @@ After August 31, 2025, TLS 1.0 and 1.1 will no longer be supported, and connecti
 
 - To verify the minimum TLS version configured for your Azure Database for MySQL Server, check the value of the `tls_version` server parameter using the MySQL command-line interface to understand what protocols are configured.
 
-#### Why was my service flagged if I’ve already configured TLS 1.2?
+#### Why was my service flagged if I've already configured TLS 1.2?
 
 Services might be incorrectly flagged due to:
 
 - Intermittent fallback to older TLS versions by legacy clients.
-- Misconfigured client libraries or connection strings that don’t enforce TLS 1.2.
+- Misconfigured client libraries or connection strings that don't enforce TLS 1.2.
 - Telemetry lag or false positives in detection logic.
 
 #### What should I do if I received a retirement notice in error?
 
 If your server or database is already configured with minimum TLS 1.2, or configured with no minimum TLS (the default setting in SQL Database and SQL Managed Instance `minimalTLSVersion` that maps to `0`) and connecting with 1.2, no action is required.
 
-#### What happens if my application or client library doesn’t support TLS 1.2?
+#### What happens if my application or client library doesn't support TLS 1.2?
 
 Connections will fail once TLS 1.0/1.1 are disabled. You must upgrade your client libraries, drivers, or frameworks to versions that support TLS 1.2.
 

azure-sql/managed-instance/identify-query-performance-issues.md

@@ -63,7 +63,7 @@ Several workarounds can mitigate PSP problems. Each workaround has associated tr
 
 - A new feature introduced with SQL Server 2022 (16.x) is [Parameter Sensitive Plan optimization](/sql/relational-databases/performance/parameter-sensitivity-plan-optimization), which attempts to mitigate most suboptimal query plans caused by parameter sensitivity. This is enabled with database compatibility level 160.
 - Use the [RECOMPILE](/sql/t-sql/queries/hints-transact-sql-query) query hint at each query execution. This workaround trades compilation time and increased CPU for better plan quality. The `RECOMPILE` option is often not possible for workloads that require a high throughput. 
-- Use the [OPTION (OPTIMIZE FOR…)](/sql/t-sql/queries/hints-transact-sql-query) query hint to override the actual parameter value with a typical parameter value that produces a plan that's good enough for most parameter value possibilities. This option requires a good understanding of optimal parameter values and associated plan characteristics.
+- Use the [OPTION (OPTIMIZE FOR...)](/sql/t-sql/queries/hints-transact-sql-query) query hint to override the actual parameter value with a typical parameter value that produces a plan that's good enough for most parameter value possibilities. This option requires a good understanding of optimal parameter values and associated plan characteristics.
 - Use the [OPTION (OPTIMIZE FOR UNKNOWN)](/sql/t-sql/queries/hints-transact-sql-query) query hint to override the actual parameter value and instead use the density vector average. You can also do this by capturing the incoming parameter values in local variables and then using the local variables within the predicates instead of using the parameters themselves. For this fix, the average density must be *good enough*.
 - Disable parameter sniffing entirely by using the [DISABLE_PARAMETER_SNIFFING](/sql/t-sql/queries/hints-transact-sql-query) query hint.
 - Use the [KEEPFIXEDPLAN](/sql/t-sql/queries/hints-transact-sql-query) query hint to prevent recompilations in cache. This workaround assumes that the good-enough common plan is the one in cache already. You can also disable automatic statistics updates to reduce the chances that the good plan will be evicted and a new bad plan will be compiled.

azure-sql/managed-instance/managed-instance-link-best-practices.md

@@ -121,7 +121,7 @@ EXEC sp_validate_certificate_ca_chain <certificate_id>
 GO 
 ```
 
-A response of `Commands completed successfully. Completion time: …` indicates the MI endpoint certificate has been successfully validated. 
+A response of `Commands completed successfully. Completion time: ...` indicates the MI endpoint certificate has been successfully validated. 
 
 > [!IMPORTANT]
 > The stored procedure `sp_validate_certificate_ca_chain` relies on host OS services to perform certificate validation, which might involve an online certificate revocation check. If the host OS is not configured to access the internet, the execution fails even if the certificate chain is valid. 

docs/connect/ado-net/sql/bulk-copy-example-setup.md

@@ -22,7 +22,7 @@ The **BulkCopyDemoMatchingColumns** and **BulkCopyDemoDifferentColumns** tables
 A few of the code samples demonstrate how to use one <xref:Microsoft.Data.SqlClient.SqlBulkCopy> class to write to multiple tables. For these samples, the **BulkCopyDemoOrderHeader** and **BulkCopyDemoOrderDetail** tables are used as the destination tables. These tables are based on the **Sales.SalesOrderHeader** and **Sales.SalesOrderDetail** tables in **AdventureWorks**.  
 
 > [!NOTE]
->  The **SqlBulkCopy** code samples are provided to demonstrate the syntax for using **SqlBulkCopy** only. If the source and destination tables are located in the same SQL Server instance, it is easier and faster to use a Transact-SQL `INSERT … SELECT` statement to copy the data.  
+>  The **SqlBulkCopy** code samples are provided to demonstrate the syntax for using **SqlBulkCopy** only. If the source and destination tables are located in the same SQL Server instance, it is easier and faster to use a Transact-SQL `INSERT ... SELECT` statement to copy the data.  
   
 ## Table setup  
 To create the tables necessary for the code samples to run correctly, you must run the following Transact-SQL statements in a SQL Server database.  

docs/connect/ado-net/sql/multiple-bulk-copy-operations.md

@@ -25,7 +25,7 @@ If you perform several bulk copy operations using the same <xref:Microsoft.Data.
 ## Example
 
 > [!IMPORTANT]
->  This sample will not run unless you have created the work tables as described in [Bulk copy example setup](bulk-copy-example-setup.md). This code is provided to demonstrate the syntax for using **SqlBulkCopy** only. If the source and destination tables are located in the same SQL Server instance, it is easier and faster to use a Transact-SQL `INSERT … SELECT` statement to copy the data.  
+>  This sample will not run unless you have created the work tables as described in [Bulk copy example setup](bulk-copy-example-setup.md). This code is provided to demonstrate the syntax for using **SqlBulkCopy** only. If the source and destination tables are located in the same SQL Server instance, it is easier and faster to use a Transact-SQL `INSERT ... SELECT` statement to copy the data.  
   
 [!code-csharp[DataWorks SqlBulkCopy_._ColumnMappingOrdersDetails#1](~/../sqlclient/doc/samples/SqlBulkCopy_ColumnMappingOrdersDetails.cs#1)]
 

docs/connect/ado-net/sql/single-bulk-copy-operations.md

@@ -46,7 +46,7 @@ The general steps for performing a bulk copy operation are as follows:
 The following console application demonstrates how to load data using the <xref:Microsoft.Data.SqlClient.SqlBulkCopy> class. In this example, a <xref:Microsoft.Data.SqlClient.SqlDataReader> is used to copy data from the **Production.Product** table in the SQL Server **AdventureWorks** database to a similar table in the same database.  
 
 > [!IMPORTANT]
->  This sample will not run unless you have created the work tables as described in [Bulk copy example setup](bulk-copy-example-setup.md). This code is provided to demonstrate the syntax for using **SqlBulkCopy** only. If the source and destination tables are located in the same SQL Server instance, it is easier and faster to use a Transact-SQL `INSERT … SELECT` statement to copy the data.  
+>  This sample will not run unless you have created the work tables as described in [Bulk copy example setup](bulk-copy-example-setup.md). This code is provided to demonstrate the syntax for using **SqlBulkCopy** only. If the source and destination tables are located in the same SQL Server instance, it is easier and faster to use a Transact-SQL `INSERT ... SELECT` statement to copy the data.  
   
 [!code-csharp[DataWorks SqlBulkCopy_WriteToServer#1](~/../sqlclient/doc/samples/SqlBulkCopy_WriteToServer.cs#1)]
 

docs/connect/php/use-table-valued-parameters.md

@@ -130,7 +130,7 @@ sqlsrv_next_result($stmt);
 
 ### Use the PDO_SQLSRV driver
 
-This is an equivalent example when using the PDO_SQLSRV driver. You can use prepare/execute with [bindParam](../../connect/php/pdostatement-bindparam.md) and specify the TVP input as a `PDO::PARAM_LOB`. If not, you'll get this error: `Operand type clash: nvarchar is incompatible with …`.
+This is an equivalent example when using the PDO_SQLSRV driver. You can use prepare/execute with [bindParam](../../connect/php/pdostatement-bindparam.md) and specify the TVP input as a `PDO::PARAM_LOB`. If not, you'll get this error: `Operand type clash: nvarchar is incompatible with ...`.
 
 ```php
 try {

docs/integration-services/azure-feature-pack-for-integration-services-ssis.md

@@ -20,6 +20,7 @@ SQL Server Integration Services (SSIS) Feature Pack for Azure is an extension th
 
 :::image type="icon" source="../includes/media/download.svg" border="false"::: **[Download SSIS Feature Pack for Azure](https://www.microsoft.com/download/details.aspx?id=104811)**
 
+- For SQL Server 2025 - [Microsoft SQL Server 2025 Integration Services Feature Pack for Azure](https://www.microsoft.com/download/details.aspx?id=108513)
 - For SQL Server 2022 - [Microsoft SQL Server 2022 Integration Services Feature Pack for Azure](https://www.microsoft.com/download/details.aspx?id=104811)
 - For SQL Server 2019 - [Microsoft SQL Server 2019 Integration Services Feature Pack for Azure](https://www.microsoft.com/download/details.aspx?id=100430)
 - For SQL Server 2017 - [Microsoft SQL Server 2017 Integration Services Feature Pack for Azure](https://www.microsoft.com/download/details.aspx?id=54798)