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: articles/postgresql/migrate/migration-service/includes/single-server/postgresql-single-server-portal-migrate.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,7 @@ Alternatively, you can initiate the migration process from the Azure Database fo
61
61
62
62
After deploying the Flexible Server, follow the steps 3 to 5 under [Configure the migration task.](#configure-the-migration-task)
63
63
64
-
### Setup tab
64
+
### Setup
65
65
66
66
The first tab is **Setup**. In case you missed it, allowlist necessary extensions as shown in It's essential to allowlist these extensions before you initiate a migration.
67
67
@@ -82,7 +82,7 @@ If the **Online** migration is selected, Logical replication must be turned on i
82
82
83
83
Select the **Next : Connect to Source** button.
84
84
85
-
### Source tab
85
+
### Connect to source
86
86
87
87
The **Source** tab prompts you to give details related to the Single Server, which is the source of the databases.
88
88
@@ -96,7 +96,7 @@ After filling out all the fields, select the **Connect to source** link. This va
96
96
97
97
Select the **Next : Select migration target** button to continue.
98
98
99
-
### Target tab
99
+
### Select migration target
100
100
101
101
The **Target** tab displays metadata for the Flexible Server target, such as subscription name, resource group, server name, location, and PostgreSQL version.
102
102
@@ -106,7 +106,7 @@ For **Server admin login name**, the tab displays the admin username used during
106
106
107
107
Select the **Next** button to select the databases to migrate.
108
108
109
-
### Select Databases for the migration tab
109
+
### Select database for migration
110
110
111
111
Under this tab, there's a list of user databases inside the Single Server. You can select and migrate up to eight databases in a single migration attempt. If there are more than eight user databases, the migration process is repeated between the source and target servers for the next set of databases. By default, selected databases with the same name on the target are overwritten.
112
112
@@ -232,7 +232,7 @@ Alternatively, you can initiate the migration process from the Azure Database fo
232
232
233
233
After deploying the Flexible Server, follow the steps 3 to 5 under [Configure the migration task.](#configure-the-migration-task)
234
234
235
-
### Setup tab
235
+
### Setup
236
236
237
237
The first tab is **Setup**. In case you missed it, allowlist necessary extensions as shown in It's essential to allowlist these extensions before you initiate a migration.
238
238
@@ -253,7 +253,7 @@ If the **Online** migration is selected, Logical replication must be turned on i
253
253
254
254
Select the **Next : Connect to Source** button.
255
255
256
-
### Source tab
256
+
### Connect to source
257
257
258
258
The **Source** tab prompts you to give details related to the Single Server, which is the source of the databases.
259
259
@@ -267,7 +267,7 @@ After filling out all the fields, select the **Connect to source** link. This va
267
267
268
268
Select the **Next : Select migration target** button to continue.
269
269
270
-
### Target tab
270
+
### Select migrfation target
271
271
272
272
The **Target** tab displays metadata for the Flexible Server target, such as subscription name, resource group, server name, location, and PostgreSQL version.
273
273
@@ -277,7 +277,7 @@ For **Server admin login name**, the tab displays the admin username used during
277
277
278
278
Select the **Next** button to select the databases to migrate.
279
279
280
-
### Select Databases for the migration tab
280
+
### Select database for the migration
281
281
282
282
Under this tab, there's a list of user databases inside the Single Server. You can select and migrate up to eight databases in a single migration attempt. If there are more than eight user databases, the migration process is repeated between the source and target servers for the next set of databases. By default, selected databases with the same name on the target are overwritten.
Copy file name to clipboardExpand all lines: articles/postgresql/migrate/migration-service/tutorial-migration-service-single-to-flexible.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,10 +5,11 @@ description: "Learn about migrating your Single Server databases to Azure Databa
5
5
author: hariramt
6
6
ms.author: hariramt
7
7
ms.reviewer: maghan, adityaduvuri
8
-
ms.date: 03/19/2024
8
+
ms.date: 06/14/2024
9
9
ms.service: postgresql
10
-
ms.custom: devx-track-azurecli
11
10
ms.topic: tutorial
11
+
ms.custom:
12
+
- devx-track-azurecli
12
13
# CustomerIntent: As a user, I want to learn how to migrate my Single Server databases to Azure Database for PostgreSQL Flexible Server using the Azure portal, so that I can take advantage of the flexibility and scalability offered by the Flexible Server.
13
14
---
14
15
@@ -19,7 +20,7 @@ ms.topic: tutorial
19
20
Using the Azure portal, you can migrate an instance of Azure Database for PostgreSQL – Single Server to Azure Database for PostgreSQL – Flexible Server. In this tutorial, we perform migration of a sample database from an Azure Database for PostgreSQL single server to a PostgreSQL flexible server using the Azure portal.
20
21
21
22
> [!div class="checklist"]
22
-
>
23
+
>
23
24
> - Configure your Azure Database for PostgreSQL Flexible Server
24
25
> - Configure the migration task
25
26
> - Monitor the migration
@@ -36,7 +37,7 @@ Using the Azure portal, you can migrate an instance of Azure Database for Postgr
36
37
37
38
---
38
39
39
-
## Post migration
40
+
## Check the migration once complete
40
41
41
42
After completing the databases, you need to manually validate the data between source and target and verify that all the objects in the target database are successfully created.
0 commit comments