You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: azure-sql/database/doc-changes-updates-release-notes-whats-new-archive.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ description: Learn about the features and documentation improvements for Azure S
5
5
author: WilliamDAssafMSFT
6
6
ms.author: wiassaf
7
7
ms.reviewer: mathoma, maghan
8
-
ms.date: 03/18/2025
8
+
ms.date: 02/19/2026
9
9
ms.service: azure-sql-database
10
10
ms.subservice: service-overview
11
11
ms.topic: whats-new
@@ -140,7 +140,7 @@ Return to [What's new in Azure SQL Database?](doc-changes-updates-release-notes-
140
140
|**JavaScript & Python bindings**| Support for JavaScript and Python SQL bindings for Azure Functions is currently in preview. For more information, see [Azure SQL bindings for Azure Functions](/azure/azure-functions/functions-bindings-azure-sql). |
141
141
|**Local development experience**| The Azure SQL Database local development experience is a combination of tools and procedures that empowers application developers and database professionals to design, edit, build/validate, publish, and run database schemas for databases directly on their workstation using an Azure SQL Database containerized environment. For more information, see [Local development experience for Azure SQL Database](local-dev-experience-overview.md). |
142
142
|**SQL Database emulator**| The Azure SQL Database emulator provides the ability to locally validate database and query design together with client application code in a simple and frictionless model as part of the application development process. The SQL Database emulator is currently in preview. For more information, see [SQL Database emulator](local-dev-experience-sql-database-emulator.md). |
143
-
|**SDK-style SQL projects**| Use [Microsoft.Build.Sql](https://www.nuget.org/packages/Microsoft.Build.Sql) for SDK-style SQL projects in the SQL Database Projects extension in Visual Studio Code. This feature is currently in preview. For more information, see [SDK-style SQL projects](/azure-data-studio/extensions/sql-database-project-extension-sdk-style-projects). |
143
+
|**SDK-style SQL projects**| Use [Microsoft.Build.Sql](https://www.nuget.org/packages/Microsoft.Build.Sql) for SDK-style SQL projects in the SQL Database Projects extension in Visual Studio Code. For more information, see [Original projects vs SDK-style projects](/sql/tools/sql-database-projects/sql-database-projects#original-projects-vs-sdk-style-projects). |
144
144
|**Azure Synapse Link for SQL for Azure SQL Database**| Azure Synapse Link for SQL enables near real-time analytics over operational data in SQL Server 2022 and Azure SQL Database. With a seamless integration between operational stores and Azure Synapse Analytics dedicated SQL pools, Azure Synapse Link for SQL enables you to run analytics, business intelligence, and machine learning scenarios on your operational data with minimum impact on source databases with a new change feed technology. For more information, see [What is Azure Synapse Link for SQL? (Preview)](/azure/synapse-analytics/synapse-link/sql-synapse-link-overview). |
145
145
|**General Purpose tier Zone redundancy GA**| Enabling zone redundancy for your provisioned and serverless General Purpose databases and elastic pools is now generally available in select regions. For more information, including region availability, see [General Purpose zone redundancy](high-availability-sla-local-zone-redundancy.md#zone-redundant-availability). |
146
146
|**Change data capture GA**| Change data capture (CDC) lets you track all the changes that occur on a database. Though this feature has been available for SQL Server for quite some time, using it with Azure SQL Database is now generally available. For more information, see [Change data capture](/sql/relational-databases/track-changes/about-change-data-capture-sql-server). |
Copy file name to clipboardExpand all lines: azure-sql/database/local-dev-experience-overview.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,11 @@
1
1
---
2
-
title: What Is the Local Development Experience?
2
+
title: What is the Local Development Experience?
3
3
titleSuffix: Azure SQL Database
4
4
description: Learn about the local development experience for Azure SQL Database.
5
5
author: croblesm
6
6
ms.author: roblescarlos
7
7
ms.reviewer: wiassaf, randolphwest
8
-
ms.date: 06/13/2025
8
+
ms.date: 02/19/2026
9
9
ms.service: azure-sql-database
10
10
ms.topic: overview
11
11
monikerRange: "=azuresql || =azuresql-db"
@@ -53,7 +53,7 @@ To streamline the local development experience, several tools and extensions are
53
53
| --- | --- | --- |
54
54
|**[Azure SQL Database Dev Container Templates](https://aka.ms/azuresql-devcontainers-repo)**| Provides preconfigured development environments, eliminating manual setup and ensuring consistency. Supports multiple popular languages. |[Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers)<br />[GitHub Codespaces](https://docs.github.com/en/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers)|
55
55
|**[SQL Server extension](/sql/tools/visual-studio-code/sql-server-develop-use-vscode)**| Enables connection, query execution, and script testing against a database, whether local or in Azure SQL Database. |[Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=ms-mssql.mssql)<br />GitHub Codespaces |
56
-
|**[SQL Database Projects extension](/azure-data-studio/extensions/sql-database-project-extension)**| Allows capturing existing database schemas, designing new objects using a declarative model, committing schemas to version control, and publishing to databases. |[Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=ms-mssql.sql-database-projects-vscode)<br />GitHub Codespaces |
56
+
|**[SQL Database Projects extension](/sql/tools/sql-database-projects/sql-database-projects#original-projects-vs-sdk-style-projects)**| Allows capturing existing database schemas, designing new objects using a declarative model, committing schemas to version control, and publishing to databases. |[Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=ms-mssql.sql-database-projects-vscode)<br />GitHub Codespaces |
Copy file name to clipboardExpand all lines: azure-sql/database/transact-sql-tsql-differences-sql-server.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: This article discusses the Transact-SQL (T-SQL) differences between
4
4
author: croblesm
5
5
ms.author: roblescarlos
6
6
ms.reviewer: wiassaf, mathoma, randolphwest
7
-
ms.date: 06/16/2025
7
+
ms.date: 02/19/2026
8
8
ms.service: azure-sql-database
9
9
ms.subservice: migration
10
10
ms.topic: reference
@@ -16,7 +16,7 @@ ms.custom:
16
16
17
17
# T-SQL differences between SQL Server and Azure SQL Database
18
18
19
-
When [migrating your database](migrate-to-database-from-sql-server.md) from SQL Server to Azure SQL Database, you might discover that your SQL Server databases require some re-engineering before they can be migrated. This article provides guidance to assist you in both performing this re-engineering and understanding the underlying reasons why the re-engineering is necessary. To detect incompatibilities and migrate databases to Azure SQL Database, use [Azure Data Migration Service](/azure/dms).
19
+
When [migrating your database](migrate-to-database-from-sql-server.md) from SQL Server to Azure SQL Database, you might discover that your SQL Server databases require some re-engineering before they can be migrated. This article provides guidance to assist you in both performing this re-engineering and understanding the underlying reasons why the re-engineering is necessary. To detect incompatibilities and migrate databases to Azure SQL Database, use [Azure Database Migration Service](/azure/dms).
Copy file name to clipboardExpand all lines: azure-sql/managed-instance/doc-changes-updates-release-notes-whats-new-archive.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ description: Learn about the features and documentation improvements for Azure S
5
5
author: MashaMSFT
6
6
ms.author: mathoma
7
7
ms.reviewer: wiassaf, randolphwest
8
-
ms.date: 01/22/2025
8
+
ms.date: 02/19/2026
9
9
ms.service: azure-sql-managed-instance
10
10
ms.subservice: service-overview
11
11
ms.topic: whats-new
@@ -114,7 +114,7 @@ The following changes were added to SQL Managed Instance and the documentation i
114
114
|**Windows Auth for Azure Active Directory principals GA**| Kerberos authentication for Azure Active Directory (Azure AD) enables Windows Authentication access to Azure SQL Managed Instance. This feature is now generally available (GA). To learn more, review [Windows Auth for Azure Active Directory principals](winauth-azuread-overview.md). |
115
115
|**Query Store hints GA**| Use query hints to optimize your query execution via the OPTION clause. This feature is now generally available (GA). To learn more, review, [Query Store hints](/sql/relational-databases/performance/query-store-hints?view=azuresqldb-mi-current&preserve-view=true)|
116
116
|**Premium-series hardware GA**| Deploy your SQL Managed Instance to the new premium-series hardware to take advantage of the latest Intel Ice Lake CPUs. The premium-series hardware is now generally available. See [Premium-series hardware](resource-limits.md#service-tier-characteristics) to learn more. |
117
-
|**SDK-style SQL projects**| Use [Microsoft.Build.Sql](https://www.nuget.org/packages/Microsoft.Build.Sql) for SDK-style SQL projects in the SQL Database Projects extension in Visual Studio Code. This feature is currently in preview. To learn more, see [SDK-style SQL projects](/azure-data-studio/extensions/sql-database-project-extension-sdk-style-projects). |
117
+
|**SDK-style SQL projects**| Use [Microsoft.Build.Sql](https://www.nuget.org/packages/Microsoft.Build.Sql) for SDK-style SQL projects in the SQL Database Projects extension in Visual Studio Code. For more information, see [Original projects vs SDK-style projects](/sql/tools/sql-database-projects/sql-database-projects#original-projects-vs-sdk-style-projects). |
118
118
|**JavaScript & Python bindings**| Support for JavaScript and Python SQL bindings for Azure Functions is currently in preview. See [Azure SQL bindings for Azure Functions](/azure/azure-functions/functions-bindings-azure-sql) to learn more. |
119
119
|**Data virtualization preview**| It's now possible to query data in external sources such as Azure Data Lake Storage Gen2 or Azure Blob Storage, joining it with locally stored relational data. This feature is currently in preview. To learn more, see [Data virtualization](data-virtualization-overview.md). |
120
120
|**Managed Instance link guidance**| We've published a number of guides for using the [Managed Instance link feature](managed-instance-link-feature-overview.md), including how to [prepare your environment](managed-instance-link-preparation.md), [configure replication by using SSMS](managed-instance-link-use-ssms-to-replicate-database.md), [configure replication via scripts](managed-instance-link-use-scripts-to-replicate-database.md), [fail over your database by using SSMS](managed-instance-link-use-ssms-to-failover-database.md), [fail over your database via scripts](managed-instance-link-use-scripts-to-failover-database.md) and some [best practices](managed-instance-link-best-practices.md) when using the link feature (currently in preview). |
description: Learn about the new features and documentation improvements for Azure SQL Managed Instance.
5
5
author: MashaMSFT
6
6
ms.author: mathoma
7
-
ms.reviewer: wiassaf, mathoma
8
-
ms.date: 12/03/2025
7
+
ms.reviewer: wiassaf, randolphwest
8
+
ms.date: 02/19/2026
9
9
ms.service: azure-sql-managed-instance
10
10
ms.subservice: service-overview
11
11
ms.topic: whats-new
@@ -38,7 +38,7 @@ The following table lists the features of Azure SQL Managed Instance that are cu
38
38
|[DATEADD number allows bigint](/sql/t-sql/functions/dateadd-transact-sql)| For `DATEADD (datepart, number, date)`, number can be expressed as a **bigint**.|
39
39
|[Endpoint policies](./service-endpoint-policies-configure.md)| Configure which Azure Storage accounts can be accessed from a SQL Managed Instance subnet. Grants an extra layer of protection against inadvertent or malicious data exfiltration.|
40
40
|[Modernization Advisor](../virtual-machines/modernization-advisor.md)| Use the Modernization Advisor in the Azure portal to help you determine if migrating to Azure SQL Managed Instance from a SQL Server VM saves you money or optimizes performance. |
41
-
|[SDK-style SQL project](/sql/azure-data-studio/extensions/sql-database-project-extension-sdk-style-projects)| Use [Microsoft.Build.Sql](https://www.nuget.org/packages/Microsoft.Build.Sql) for SDK-style SQL projects in the SQL Database Projects extension in Visual Studio Code. SDK-style SQL projects are especially advantageous for applications shipped through pipelines or built in cross-platform environments.|
41
+
|[SDK-style SQL project](/sql/tools/sql-database-projects/sql-database-projects)| Use [Microsoft.Build.Sql](https://www.nuget.org/packages/Microsoft.Build.Sql) for SDK-style SQL projects in the SQL Database Projects extension in Visual Studio Code. SDK-style SQL projects are especially advantageous for applications shipped through pipelines or built in cross-platform environments.|
42
42
|[Service Broker](/sql/database-engine/configure-windows/sql-server-service-broker)| Support for cross-instance message exchange using Service Broker between instances of Azure SQL Managed Instance, and between SQL Server and Azure SQL Managed Instance. |
43
43
|[SQL Server 2025 update policy](update-policy.md#sql-server-2025-update-policy)| Align your SQL managed instance database format with the SQL Server 2025 database engine. |
44
44
|[Vector data type and functions](/sql/t-sql/data-types/vector-data-type?view=azuresqlmi-current&preserve-view=true)| Working with vector data is now easier in Azure SQL Managed Instance with the introduction of a new [vector data type](/sql/t-sql/data-types/vector-data-type?view=azuresqlmi-current&preserve-view=true) and [vector functions](/sql/t-sql/functions/vector-functions-transact-sql?view=azuresqlmi-current&preserve-view=true). For more information, see [Intelligent applications with Azure SQL Managed Instance](ai-artificial-intelligence-intelligent-applications.md#vectors). |
Copy file name to clipboardExpand all lines: azure-sql/managed-instance/managed-instance-link-migrate.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ description: Learn how to use the Managed Instance link to migrate your SQL Serv
5
5
author: danimir
6
6
ms.author: danil
7
7
ms.reviewer: mathoma, randolphwest
8
-
ms.date: 01/26/2026
8
+
ms.date: 02/19/2026
9
9
ms.service: azure-sql-managed-instance
10
10
ms.subservice: data-movement
11
11
ms.topic: how-to
@@ -61,7 +61,7 @@ You can use the following tools to discover SQL sources in your environment:
61
61
62
62
After data sources have been discovered, assess any on-premises SQL Server instances that can be migrated to Azure SQL Managed Instance to identify migration blockers or compatibility issues.
63
63
64
-
You can use [Azure right-sized recommendations](/azure/dms/ads-sku-recommend) to assess your source SQL Server instance.
64
+
You can use the [migration readiness assessment](/sql/sql-server/azure-arc/migration-assessment) to assess your source SQL Server instance.
65
65
66
66
For detailed guidance, review [pre-migration](../migration-guides/managed-instance/sql-server-to-managed-instance-guide.md).
Copy file name to clipboardExpand all lines: azure-sql/migration-guides/modernization.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Frequently Asked Questions about migrating from SQL Server to Azure
4
4
author: rwestMSFT
5
5
ms.author: randolphwest
6
6
ms.reviewer: dmarinkovic
7
-
ms.date: 01/26/2026
7
+
ms.date: 02/19/2026
8
8
ms.service: azure-sql-database
9
9
ms.topic: faq
10
10
ms.collection:
@@ -274,7 +274,7 @@ See the [SQL Database and SQL Managed Instance](../database/business-continuity-
274
274
275
275
#### How do I obtain better performance by moving on-premises SQL Server to SQL Managed Instance, SQL Database or SQL VM?
276
276
277
-
Moving from on-premises provides you with performance benefits due to the latest SQL Server database engine features, cloud scaling flexibility, and the newest generation of underlying hardware. [Find out why your SQL Server data belongs on Azure](https://azure.microsoft.com/blog/find-out-why-your-sql-server-data-belongs-on-azure/). You can also read a recently published [study by Principled Technologies](https://www.principledtechnologies.com/Microsoft/Azure-SQL-Managed-Instance-0522.pdf) benchmarking SQL Managed Instance and SQL Server on Amazon Web Services (AWS) RDS. It's important to ensure a [proper sizing based on your requirements](/azure/dms/migration-using-azure-data-studio) for CPU, memory, and [storage](../managed-instance/resource-limits.md#data-and-log-storage) (IOPS, latency, transaction log throughput, and size). SQL Managed Instance and SQL Database also provide a choice between different [hardware configurations](../managed-instance/sql-managed-instance-paas-overview.md#vcore-based-purchasing-model) and [service tiers](../managed-instance/resource-limits.md#service-tier-characteristics) that provide other means to reach target performance. Applications can also take advantage of [read scale-out](../database/read-scale-out.md) abilities including with [named replicas](../database/service-tier-hyperscale-replicas.md) and [geo-replicas](../database/active-geo-replication-overview.md), and techniques such as [database sharding](../database/elastic-scale-introduction.md).
277
+
Moving from on-premises provides you with performance benefits due to the latest SQL Server database engine features, cloud scaling flexibility, and the newest generation of underlying hardware. [Find out why your SQL Server data belongs on Azure](https://azure.microsoft.com/blog/find-out-why-your-sql-server-data-belongs-on-azure/). You can also read a recently published [study by Principled Technologies](https://www.principledtechnologies.com/Microsoft/Azure-SQL-Managed-Instance-0522.pdf) benchmarking SQL Managed Instance and SQL Server on Amazon Web Services (AWS) RDS. It's important to ensure a [proper sizing based on your requirements](/sql/sql-server/azure-arc/migration-assessment) for CPU, memory, and [storage](../managed-instance/resource-limits.md#data-and-log-storage) (IOPS, latency, transaction log throughput, and size). SQL Managed Instance and SQL Database also provide a choice between different [hardware configurations](../managed-instance/sql-managed-instance-paas-overview.md#vcore-based-purchasing-model) and [service tiers](../managed-instance/resource-limits.md#service-tier-characteristics) that provide other means to reach target performance. Applications can also take advantage of [read scale-out](../database/read-scale-out.md) abilities including with [named replicas](../database/service-tier-hyperscale-replicas.md) and [geo-replicas](../database/active-geo-replication-overview.md), and techniques such as [database sharding](../database/elastic-scale-introduction.md).
278
278
279
279
#### How can I compare SQL Managed Instance performance to SQL Server performance?
0 commit comments