Skip to content

Commit f26eacb

Browse files
Merge pull request #269118 from markingmyname/finalpgmig
[PostgreSQL] minor edits before Ga release
2 parents a46c826 + 95ad3bf commit f26eacb

File tree

2 files changed

+0
-9
lines changed

2 files changed

+0
-9
lines changed

articles/postgresql/migrate/migration-service/includes/single-server/postgresql-single-server-cli-migrate.md

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -136,11 +136,6 @@ Note these essential points for the command response:
136136
- The time that the `Migrating Data` substate takes to finish depends on the size of the databases that are migrated.
137137
- The migration moves to the `Succeeded` state as soon as the `Migrating Data` substate finishes successfully. If there's a problem at the `Migrating Data` substate, the migration moves into a `Failed` state.
138138

139-
> [!NOTE]
140-
> The Single to Flex migration service is available in all Azure regions and supports **Offline** migrations. **Online migrations preview** is available in all public clouds and China regions. In other regions, the user can enable Online migration at a subscription level by registering for the **Online PostgreSQL migrations to Azure PostgreSQL Flexible server** preview feature, as shown in the image.
141-
142-
:::image type="content" source="../../media/tutorial-migration-service-single-to-flexible/online-migration-feature-switch.png" alt-text="Screenshot of online PostgreSQL migrations to Azure PostgreSQL Flexible server." lightbox="../../media/tutorial-migration-service-single-to-flexible/online-migration-feature-switch.png":::
143-
144139
#### Setup replication
145140

146141
If the **Online** migration preview is selected, Logical replication must be turned on in the source Single server. If it isn't turned on, the migration service automatically turns on logical replication at the source Single server when the `SetupLogicalReplicationOnSourceDBIfNeeded` parameter is passed with a value of `true` in the accompanying JSON file. Replication can also be set up manually at the source after starting the migration using the command below. Either approach of turning on logical replication restarts the source Single server.

articles/postgresql/migrate/migration-service/includes/single-server/postgresql-single-server-portal-migrate.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -82,10 +82,6 @@ The first tab is **Setup**. In case you missed it, allowlist necessary extension
8282

8383
It's always a good practice to choose **Validate** or **Validate and Migrate** option to perform premigration validations before running the migration.
8484

85-
**Migration mode** allows you to pick the mode for the migration. **Offline** is the default option. **Online migrations preview** is available in all public clouds and China regions. In other regions, the user can enable Online migration at a subscription level by registering for the **Online PostgreSQL migrations to Azure PostgreSQL Flexible server** preview feature, as shown in the image.
86-
87-
:::image type="content" source="../../media/tutorial-migration-service-single-to-flexible/online-migration-feature-switch.png" alt-text="Screenshot of online PostgreSQL migrations to Azure PostgreSQL Flexible server." lightbox="../../media/tutorial-migration-service-single-to-flexible/online-migration-feature-switch.png":::
88-
8985
If the **Online** migration preview is selected, Logical replication must be turned on in the source Single server. If it's not turned on, the migration service automatically turns on logical replication at the source Single server. Replication can also be set up manually under the **Replication** tab in the Single server-side pane by setting the Azure replication support level to **Logical**. Either approach restarts the source single server.
9086

9187
Select the **Next : Connect to Source** button.

0 commit comments

Comments
 (0)