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: data-migration/sql-server/overview.md
+28-10Lines changed: 28 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,10 @@
1
1
---
2
-
title: "Migrate from SQL Server Overview"
2
+
title: Migrate from SQL Server Overview
3
3
description: "Follow the five steps to a successful SQL Server migration to Azure SQL: Discovery, Assessment, Business case, Conversion, and Migration."
4
-
author: abhims14
5
-
ms.author: abhishekum
6
-
ms.reviewer: randolphwest, mathoma
7
-
ms.date: 02/19/2026
4
+
author: rwestMSFT
5
+
ms.author: randolphwest
6
+
ms.reviewer: abhishekum, mathoma
7
+
ms.date: 04/13/2026
8
8
ms.service: azure-sql-managed-instance
9
9
ms.subservice: migration-guide
10
10
ms.topic: how-to
@@ -26,13 +26,13 @@ This article describes the five phases for a successful cloud migration from SQL
26
26
-[Conversion](#conversion)
27
27
-[Migration](#migration)
28
28
29
-
:::image type="content" source="media/migration-process-flow-small.png" alt-text="Diagram that shows a migration process flow.":::
29
+
:::image type="content" source="media/overview/migration-process-flow-small.png" alt-text="Diagram that shows a migration process flow.":::
30
30
31
31
## Discovery
32
32
33
33
When you start your cloud migration journey, it's critical to discover installed software inventory, web apps, and SQL Server instances and databases on servers running in your on-premises environment. This discovery helps you tailor a migration path to Azure SQL.
34
34
35
-
The Azure Migrate appliance performs this discovery using the Windows OS domain or non-domain credentials, or SQL Server authentication credentials that have access to your SQL Server instances and databases. This discovery process is agentless, meaning that nothing is installed on the servers. The Azure Migrate appliance supports discovery on various virtualization platforms like VMware, Microsoft Hyper-V, and physical environments.
35
+
The Azure Migrate appliance performs this discovery using the Windows OS domain or non-domain credentials, or SQL Server authentication credentials that have access to your SQL Server instances and databases. This discovery process is agentless, meaning that you don't install anything on the servers. The Azure Migrate appliance supports discovery on various virtualization platforms like VMware, Microsoft Hyper-V, and physical environments.
36
36
37
37
To learn how to discover your on-premises SQL Servers, see the [Discover](pre-migration.md#discover) section later in this article.
38
38
@@ -64,14 +64,32 @@ After the assessment determines the readiness and the recommended Azure SQL depl
64
64
65
65
## Conversion
66
66
67
-
In heterogeneous migrations, while you migrate data from one database to another, it's important to convert database schema and objects into equivalent Transact-SQL syntax. The source and target databases engines are different. These database objects include tables, indexes, views, data types, Transact-SQL statements, stored procedures, and functions.
67
+
In heterogeneous migrations, while you migrate data from one database to another, make sure you convert the database schema and objects into equivalent Transact-SQL syntax. The source and target database engines are different. These database objects include tables, indexes, views, data types, Transact-SQL statements, stored procedures, and functions.
68
68
69
69
> [!NOTE]
70
-
> The conversion phase isn't needed for SQL Server to Azure SQL migrations. SQL Server Migration Assistant (SSMA) performs the conversion while migrating to any of the Azure SQL targets. SSMA supports multiple sources, such as Oracle, MySQL, DB2, Sybase, and Microsoft Access, for both conversion and data migration.
70
+
> You don't need the conversion phase for SQL Server to Azure SQL migrations. SQL Server Migration Assistant (SSMA) performs the conversion while migrating to any of the Azure SQL targets. SSMA supports multiple sources, such as Oracle, MySQL, DB2, Sybase, and Microsoft Access, for both conversion and data migration.
71
71
72
72
## Migration
73
73
74
-
Migration is the last stage of this process, in which the data is migrated from source database to the target database. Azure Database Migration Service (DMS) is a fully managed service designed to enable seamless migrations from multiple database sources to Azure data platforms. DMS offers minimal downtime, high reliability, and resiliency. DMS is available via various clients, the Azure portal, PowerShell, and Azure CLI. To learn more about Azure Database Migration service, see [What is Azure Database Migration Service?](/azure/dms/dms-overview)
74
+
Migration is the last stage of this process, in which you migrate data from the source database to the target database.
75
+
76
+
### Choose a migration method
77
+
78
+
Choose from multiple migration methods depending on your target platform and acceptable application downtime.
79
+
80
+
### SQL Managed Instance link (near zero downtime to Azure SQL Managed Instance)
81
+
82
+
If you [enable Azure Arc for your SQL Server instance](managed-instance/overview.md), you can use [Managed Instance link](/azure/azure-sql/managed-instance/managed-instance-link-feature-overview?view=azuresql&preserve-view=true) to perform an online migration to Azure SQL Managed Instance. The link feature uses distributed availability groups to replicate data from SQL Server to SQL Managed Instance in near real-time. This approach allows your source database to remain operational while data is continuously synchronized to the target environment. Downtime is limited to the final cutover phase when you switch your application to the migrated database.
83
+
84
+
### Backup and restore (one-time migration to SQL Server on Azure VM)
85
+
86
+
If planned downtime is acceptable, use a one-time backup and restore migration to [SQL Server on Azure Virtual Machines](/ssms/migrate/upgrade-sql-server#upgrade-sql-server). In this offline migration approach, application downtime begins when the migration starts and continues until the database restore is completed on the target environment.
87
+
88
+
### Azure Database Migration Service (all targets)
89
+
90
+
Azure Database Migration Service (Azure DMS) is a fully managed service that supports migrations from multiple database sources to Azure data platforms with minimal downtime, high reliability, and resiliency. You can access Azure DMS through the Azure portal, PowerShell, and Azure CLI. To learn more, see [What is Azure Database Migration Service](/azure/dms/dms-overview).
91
+
92
+
[Azure DMS](/azure/dms/resource-scenario-status) supports both offline (one-time) migration to Azure SQL Database, SQL Managed Instance, or SQL Server on Azure VM, and online (continuous backup restore) migrations for SQL Managed Instance and Azure VM, so you can choose a migration approach based on downtime requirements.
Copy file name to clipboardExpand all lines: docs/database-engine/sql-database-engine.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,9 +18,11 @@ The SQL Database Engine is the common underlying engine behind all Microsoft SQL
18
18
19
19
For millions of customers worldwide, in every industry and level of organization, the Microsoft SQL Database Engine is the database service for secure data processing and storage. Demanding applications can reliably read and modify information while preserving integrity at scale. The SQL Database Engine runs as a service that accepts client connections and then executes the requested operations against databases. Secured with enterprise-class data access and encryption features, and with built-in high availability and database recovery features, the SQL Database Engine is a complete database platform.
20
20
21
-
## Multimodal databaseengine
21
+
<aid="multimodal-database-engine"></a>
22
22
23
-
The SQL Database Engine is a multimodal database engine with purpose-built storage formats, purpose-built index structures, and a single query optimizer that makes cost-based decisions across all data models.
23
+
## Multi-model database engine
24
+
25
+
The SQL Database Engine is a multi-model database engine with purpose-built storage formats, purpose-built index structures, and a single query optimizer that makes cost-based decisions across all data models.
24
26
25
27
Products that use the SQL Database Engine can be the enterprise-class online transactional processing (OLTP), online analytical processing (OLAP), or non-relational solution for your modern applications. Relational, normalized data might be common for databases, but the SQL Database Engine supports many data models and data formats.
Copy file name to clipboardExpand all lines: docs/linux/sql-server-linux-release-notes-2017.md
+13-12Lines changed: 13 additions & 12 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 contains the release notes and supported features for
4
4
author: rwestMSFT
5
5
ms.author: randolphwest
6
6
ms.reviewer: amitkh, atsingh
7
-
ms.date: 03/10/2026
7
+
ms.date: 04/14/2026
8
8
ms.service: sql
9
9
ms.subservice: linux
10
10
ms.topic: release-notes
@@ -46,11 +46,11 @@ Most existing client tools that target [!INCLUDE [ssNoVersion](../includes/ssnov
46
46
47
47
## Latest versions for all packages
48
48
49
-
This section lists the latest versions of each package per distribution, for [!INCLUDE [ssSQL17](../includes/sssql17-md.md)]. The following table shows the most recent release, which is **CU 31 GDR (Mar 2026)**. For full release history, see [Release history for SQL Server 2017 on Linux](/troubleshoot/sql/releases/linux/release-history-2017).
49
+
This section lists the latest versions of each package per distribution, for [!INCLUDE [ssSQL17](../includes/sssql17-md.md)]. The following table shows the most recent release, which is **CU 31 GDR (Apr 2026)**. For full release history, see [Release history for SQL Server 2017 on Linux](/troubleshoot/sql/releases/linux/release-history-2017).
50
50
51
51
| Version | Release | Date | Build | KB article |
52
52
| --- | --- | --- | --- | --- |
53
-
|[!INCLUDE [ssSQL17](../includes/sssql17-md.md)]| CU 31 GDR | 2026-03-10| 14.0.3520.4|[KB 5077471](https://support.microsoft.com/help/5077471)|
53
+
|[!INCLUDE [ssSQL17](../includes/sssql17-md.md)]| CU 31 GDR | 2026-04-14| 14.0.3525.1|[KB 5084818](https://support.microsoft.com/help/5084818)|
54
54
55
55
The latest GDR release includes the Azure Connect Pack for [!INCLUDE [ssSQL17](../includes/sssql17-md.md)].
56
56
@@ -60,18 +60,18 @@ The latest GDR release includes the Azure Connect Pack for [!INCLUDE [ssSQL17](.
60
60
| Distribution | Package name | Package version | Download |
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments