Merge pull request #36586 from MicrosoftDocs/main

Auto Publish – main to live - 2026-02-09 18:30 UTC

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

.openpublishing.redirection.azure-data-studio.json

@@ -899,6 +899,11 @@
       "source_path": "docs/sql-operations-studio/what-is.md",
       "redirect_url": "/azure-data-studio/what-is-azure-data-studio",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/relational-databases/security/encryption/always-encrypted-query-columns-ads.md",
+      "redirect_url": "/sql/relational-databases/security/encryption/always-encrypted-query-columns-ssms",
+      "redirect_document_id": false
     }
   ]
 }

docs/relational-databases/database-lifecycle-management.md

@@ -4,7 +4,7 @@ description: Learn how to use database lifecycle management in SQL Server to man
 author: MashaMSFT
 ms.author: mathoma
 ms.reviewer: randolphwest
-ms.date: 03/11/2025
+ms.date: 02/06/2026
 ms.service: sql
 ms.subservice: supportability
 ms.topic: concept-article
@@ -31,7 +31,7 @@ helpviewer_keywords:
   - "Database connectivity"
 monikerRange: "=azuresqldb-current || >=sql-server-2016 || >=sql-server-linux-2017 || =azuresqldb-mi-current || =fabric-sqldb"
 ---
-# Database Lifecycle Management
+# Database lifecycle management
 
 [!INCLUDE [SQL Server Azure SQL Database Azure SQL Managed Instance FabricSQLDB](../includes/applies-to-version/sql-asdb-asdbmi-fabricsqldb.md)]
 
@@ -45,8 +45,8 @@ For tools, tutorials, and more information, see the following articles:
 
 - [SQL database projects](../tools/sql-database-projects/sql-database-projects.md)
 - [Install SQL Server Data Tools (SSDT) for Visual Studio](../ssdt/download-sql-server-data-tools-ssdt.md)
-- [Azure SQL Database Projects extension](/azure-data-studio/extensions/sql-database-project-extension)
-- [Getting started with the SQL Database Projects extension](/azure-data-studio/extensions/sql-database-project-extension-getting-started)
+- [SQL Database Projects extension](../tools/visual-studio-code-extensions/sql-database-projects/sql-database-projects-extension.md)
+- [Get started with the SQL Database Projects extension](../tools/visual-studio-code-extensions/sql-database-projects/getting-started-sql-database-projects-extension.md)
 
 **SqlPackage**
 
@@ -70,4 +70,3 @@ For tools, tutorials, and more information, see the following articles:
 ## Related content
 
 - [Microsoft Modern Lifecycle Policy](/lifecycle/policies/modern)
-

docs/relational-databases/errors-events/mssqlserver-35250-database-engine-error.md

@@ -24,7 +24,7 @@ helpviewer_keywords:
 | Event Source | MSSQLSERVER |
 | Component | SQLEngine |
 | Symbolic Name | HADR_PRIMARYNOTACTIVE |
-| Message Text | The connection to the primary replica isn't active. The command can't be processed. |
+| Message Text | The connection to the primary replica is not active. The command cannot be processed. |
 
 ## Explanation
 

docs/relational-databases/performance/query-store-usage-scenarios.md

@@ -110,10 +110,8 @@ Plan after missing index creation (plan_id  = 15, below) now has Index Seek (Non
 
 Based on analysis you would likely keep the index as query performance has been improved.  
 
-## <a name="CEUpgrade"></a> Keep performance stability during the upgrade to newer [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]  
-Prior to [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)], users were exposed to the risk of performance regression during the upgrade to the latest platform version. The reason for that was the fact that latest version of Query Optimizer became active immediately once new bits are installed.  
-  
-Starting with [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] all Query Optimizer changes are tied to the latest [database compatibility level](../../relational-databases/databases/view-or-change-the-compatibility-level-of-a-database.md), so plans are not changed right at point of upgrade but rather when a user changes the `COMPATIBILITY_LEVEL` to the latest one. This capability, in combination with Query Store gives you a great level of control over the query performance in the upgrade process. Recommended upgrade workflow is shown in the following picture:  
+## <a name="CEUpgrade"></a> Keep performance stability during upgrade  
+Query Optimizer changes are tied to the latest [database compatibility level](../../relational-databases/databases/view-or-change-the-compatibility-level-of-a-database.md), so plans are not changed right at point of upgrade but rather when a user changes the `COMPATIBILITY_LEVEL` to the latest one. This capability, in combination with Query Store gives you a great level of control over the query performance in the upgrade process. Recommended upgrade workflow is shown in the following picture:  
 
 ![Diagram showing the recommended upgrade workflow.](../../relational-databases/performance/media/query-store-usage-5.png "query-store-usage-5")  
 

docs/relational-databases/security/encryption/always-encrypted-query-columns-ads.md

@@ -4,7 +4,7 @@ description: "Learn about SQL Server Data Tools (SSDT). See how to install this
 author: dzsquared
 ms.author: drskwier
 ms.reviewer: randolphwest
-ms.date: 12/03/2025
+ms.date: 02/06/2026
 ms.service: sql
 ms.subservice: ssdt
 ms.topic: install-set-up-deploy
@@ -149,7 +149,7 @@ To download and install SSDT for Visual Studio 2017, or an older version of SSDT
 
 - [SSDT Team Blog](/archive/blogs/ssdt/)
 - [DACFx API Reference](/dotnet/api/microsoft.sqlserver.dac)
-- [SQL Database Projects extension](/azure-data-studio/extensions/sql-database-project-extension)
+- [SQL Database Projects extension](../tools/visual-studio-code-extensions/sql-database-projects/sql-database-projects-extension.md)
 - [What are SQL database projects?](../tools/sql-database-projects/sql-database-projects.md)
 - [SSIS How to Create an ETL Package](../integration-services/ssis-how-to-create-an-etl-package.md)
 - [Analysis Services tutorials](/analysis-services/analysis-services-tutorials-ssas)

docs/ssdt/download-sql-server-data-tools-ssdt.md

@@ -4,7 +4,7 @@ description: Create database syntax for SQL Server and all SQL Database Engine p
 author: markingmyname
 ms.author: maghan
 ms.reviewer: wiassaf, dnethi, randolphwest
-ms.date: 10/01/2025
+ms.date: 02/06/2026
 ms.service: sql
 ms.subservice: t-sql
 ms.topic: reference
@@ -1479,7 +1479,7 @@ CREATE DATABASE MyLedgerDB
 In Azure Synapse, this statement can be used with an Azure SQL Database server to create a dedicated SQL pool. With this statement, you specify the database name, collation, maximum size, edition, and service objective.
 
 - `CREATE DATABASE` is supported for standalone dedicated SQL pools (formerly SQL DW) using Gen2 service levels.
-- `CREATE DATABASE` isn't supported for dedicated SQL pools in an Azure Synapse Analytics workspace. Instead, [use the Azure portal](/azure-data-studio/quickstart-sql-dw).
+- `CREATE DATABASE` isn't supported for dedicated SQL pools in an Azure Synapse Analytics workspace. Instead, use the Azure portal.
 - `CREATE DATABASE` is supported for serverless SQL pools in Azure Synapse Analytics.
 
 ## Syntax

docs/t-sql/statements/create-database-transact-sql.md

@@ -4,7 +4,7 @@ description: SQL query and management tools for SQL Server, Azure SQL (Azure SQL
 author: rwestMSFT
 ms.author: randolphwest
 ms.reviewer: erinstellato, iqrashaikh, mbarickman, drskwier, roblescarlos
-ms.date: 10/28/2025
+ms.date: 02/06/2026
 ms.service: sql
 ms.subservice: tools-other
 ms.topic: overview