Merge pull request #264278 from MicrosoftDocs/release-preview-postgresql-migration-service

[PostgreSQL] New migration service release preview--scheduled release at 10AM of 1/30

Author: huypub

articles/postgresql/TOC.yml

@@ -12,32 +12,6 @@
     items:
     - name: SSL root certificate expiring
       href: single-server/concepts-certificate-rotation.md
-- name: Shared documentation
-  items:
-  - name: Migration
-    items:
-      - name: Migrate Azure Database for PostgreSQL - Single Server to Azure Database for PostgreSQL - Flexible Server
-        items:
-          - name: Migration tool - Concepts
-            href: migrate/concepts-single-to-flexible.md
-          - name: Migration tool - Azure portal
-            href: migrate/how-to-migrate-single-to-flexible-portal.md
-          - name: Migration tool - Azure CLI
-            href: migrate/how-to-migrate-single-to-flexible-cli.md
-          - name: Common errors
-            href: migrate/common-errors-and-special-scenarios-fms.md
-          - name: Best practices for a seamless migration
-            href: migrate/best-practices-seamless-migration-single-to-flexible.md
-          - name: Troubleshoot networking and connectivity issues
-            href: migrate/troubleshooting-networking-and-connectivity-issues.md  
-      - name: Migrate data with pg_dump
-        href: migrate/how-to-migrate-using-dump-and-restore.md
-        displayName: pg_dump, pg_restore
-      - name: Minimal-downtime migration with DMS
-        href: single-server/how-to-migrate-online.md
-        displayName: dms, data migration service
-      - name: Migrate from Oracle
-        href: single-server/how-to-migrate-from-oracle.md
   - name: Versioning policy
     href: flexible-server/concepts-version-policy.md
     displayName: version, postgresql
@@ -434,7 +408,49 @@
         - name: Optimize performance when using pgvector
           href: flexible-server/how-to-optimize-performance-pgvector.md
     - name: pg_azure_storage
-      href: flexible-server/reference-pg-azure-storage.md 
+      href: flexible-server/reference-pg-azure-storage.md
+- name: Migration
+  items:
+  - name: Migrate Single Server to Flexible Server
+    items:
+    - name: Migration tool - Concepts
+      href: migrate/concepts-single-to-flexible.md
+    - name: Migration tool - Azure portal
+      href: migrate/how-to-migrate-single-to-flexible-portal.md
+    - name: Migration tool - Azure CLI
+      href: migrate/how-to-migrate-single-to-flexible-cli.md
+    - name: Best practices for a seamless migration
+      href: migrate/best-practices-seamless-migration-single-to-flexible.md
+    - name: Troubleshoot networking and connectivity issues
+      href: migrate/troubleshooting-networking-and-connectivity-issues.md  
+  - name: Migration Service
+    items:
+    - name: Overview
+      href: migrate/migration-service/concepts-migration-service-postgresql.md
+    - name: Tutorials
+      items:
+      - name: Migrate from on-premises and Azure VM
+        href: migrate/migration-service/tutorial-migration-service-offline-iaas.md
+      - name: Migrate from AWS RDS
+        href: migrate/migration-service/tutorial-migration-service-offline-aws.md
+    - name: Concepts
+      items:
+      - name: Premigration validation
+        href: migrate/migration-service/concepts-premigration-migration-service.md
+      - name: Best practices
+        href: migrate/migration-service/best-practices-migration-service-postgresql.md
+      - name: Known issues and limitations
+        href: migrate/migration-service/concepts-known-issues-migration-service.md
+    - name: How-to guides
+      items:
+      - name: Network setup
+        href: migrate/migration-service/how-to-network-setup-migration-service.md
+  - name: Migrate data with pg_dump
+    href: migrate/how-to-migrate-using-dump-and-restore.md
+  - name: Minimal-downtime migration with DMS
+    href: single-server/how-to-migrate-online.md
+  - name: Migrate from Oracle
+    href: single-server/how-to-migrate-from-oracle.md
 - name: Azure Database for PostgreSQL - Single Server
   expanded: false
   items:

articles/postgresql/migrate/concepts-single-to-flexible.md

@@ -52,7 +52,7 @@ The migration tool comes with a simple, wizard-based experience on the Azure por
 
     :::image type="content" source="./media/concepts-single-to-flexible/flexible-overview.png" alt-text="Screenshot of the flexible Overview page." lightbox="./media/concepts-single-to-flexible/flexible-overview.png":::
 
-4. Select the **Migrate from Single Server** button to start a migration from Single Server to Flexible Server. If this is the first time you're using the migration tool, an empty grid appears with a prompt to begin your first migration.
+4. Select the **Create** button to start a migration from Single Server to Flexible Server. If this is the first time you're using the migration tool, an empty grid appears with a prompt to begin your first migration.
 
     :::image type="content" source="./media/concepts-single-to-flexible/flexible-migration-grid.png" alt-text="Screenshot of the Migration tab in flexible." lightbox="./media/concepts-single-to-flexible/flexible-migration-grid.png":::
 
@@ -89,6 +89,8 @@ The first tab is **Setup**. Just in case you missed it, allowlist necessary exte
 
 **Migration name** is the unique identifier for each migration to this Flexible Server target. This field accepts only alphanumeric characters and doesn't accept any special characters except a hyphen (-). The name can't start with a hyphen and should be unique for a target server. No two migrations to the same Flexible Server target can have the same name.
 
+**Source server type** indicates the source. In this case, it is Azure Database for PostgreSQL Single server
+
 **Migration Option** gives you the option to perform validations before triggering a migration. You can pick any of the following options
  - **Validate** - Checks your server and database readiness for migration to the target.
  - **Migrate** - Skips validations and starts migrations.
@@ -102,42 +104,46 @@ It's always a good practice to choose **Validate** or **Validate and Migrate** o
 
 If **Online** migration is selected, it requires Logical replication to be turned on in the source Single server. If it's not turned on, the migration tool automatically turns on logical replication at the source Single server. Replication can also be set up manually under **Replication** tab in the Single server side pane by setting the Azure replication support level to **Logical**. Either approach restarts the source single server.
 
-Select the **Next** button.
+Select the **Next : Connect to Source** button.
 
 ### Source tab
 
 The **Source** tab prompts you to give details related to the Single Server that is the source of the databases.
 
-:::image type="content" source="./media/concepts-single-to-flexible/flexible-migration-source.png" alt-text="Screenshot of source database server details." lightbox="./media/concepts-single-to-flexible/flexible-migration-source.png":::
-
 After you make the **Subscription** and  **Resource Group** selections, the dropdown list for server names shows Single Servers under that resource group across regions. Select the source that you want to migrate databases from. You can migrate databases from a Single Server to a target Flexible Server in the same region. Cross region migrations are enabled only for servers in India, China and UAE.
 
 After you choose the Single Server source, the **Location**, **PostgreSQL version**, and **Server admin login name** boxes are populated automatically. The server admin login name is the admin username used to create the Single Server. In the **Password** box, enter the password for that admin user. The migration tool performs the migration of single server databases as the admin user.
 
-After filling out all the fields, select the **Next** button.
+After filling out all the fields, click the **Connect to source** link. This validates that the source server details entered are correct and source server is reachable.
+
+:::image type="content" source="./media/concepts-single-to-flexible/flexible-migration-source.png" alt-text="Screenshot of source database server details." lightbox="./media/concepts-single-to-flexible/flexible-migration-source.png":::
+
+Select the **Next : Select migration target** button to continue.
 
 ### Target tab
 
-The **Target** tab displays metadata for the Flexible Server target, like subscription name, resource group, server name, location, and PostgreSQL version. 
+The **Target** tab displays metadata for the Flexible Server target, such as subscription name, resource group, server name, location, and PostgreSQL version. 
 
 :::image type="content" source="./media/concepts-single-to-flexible/flexible-migration-target.png" alt-text="Screenshot of target database server details." lightbox="./media/concepts-single-to-flexible/flexible-migration-target.png":::
 
-For **Server admin login name**, the tab displays the admin username used during the creation of the Flexible Server target. Enter the corresponding password for the admin user.
+For **Server admin login name**, the tab displays the admin username used during the creation of the Flexible Server target. Enter the corresponding password for the admin user. After filling out the password, click the **Connect to target** link. This validates that the target server details entered are correct and target server is reachable.
 
-Select the **Next** button.
+Click the **Next** button to select the databases to migrate.
 
 ### Select Database(s) for Migration tab
 
-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.
+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.
 
 :::image type="content" source="./media/concepts-single-to-flexible/flexible-migration-database.png" alt-text="Screenshot of Databases to migrate." lightbox="./media/concepts-single-to-flexible/flexible-migration-database.png":::
 
 >[!NOTE]
 > The tool migrates only user databases. System databases or template databases such as template0, template1 will not be migrated.
 
-### Review
+Click the **Next** button to review the details.
+
+### Summary
 
-The **Review** tab summarizes all the details for creating the validation or migration. Review the details and click on the start button.
+The **Summary** tab summarizes all the details for creating the validation or migration. Review the details and click on the start button.
 
 :::image type="content" source="./media/concepts-single-to-flexible/flexible-migration-review.png" alt-text="Screenshot of details to review for the migration." lightbox="./media/concepts-single-to-flexible/flexible-migration-review.png":::
 
@@ -147,7 +153,7 @@ After you click the start button, a notification appears in a few seconds to say
 
 :::image type="content" source="./media/concepts-single-to-flexible/flexible-migration-monitor.png" alt-text="Screenshot of recently created migration details." lightbox="./media/concepts-single-to-flexible/flexible-migration-monitor.png":::
 
-The grid that displays the migrations has these columns: **Name**, **Status**,  **Source DB server**, **Resource group**, **Region**, **Databases**, and **Start time**. The entries are displayed in the descending order of the start time with the most recent entry on the top.
+The grid that displays the migrations has these columns: **Name**, **Status**, **Migration type**, **Migration mode**, **Source server**, **Source server type**, **Databases**, **Start time** and **Duration**. The entries are displayed in the descending order of the start time with the most recent entry on the top.
 
 You can use the refresh button to refresh the status of the validation or migration.
 You can also select the migration name in the grid to see the associated details.
@@ -164,16 +170,16 @@ The validation moves to the **Succeeded** state if all validations are either in
 
 :::image type="content" source="./media/concepts-single-to-flexible/validation-successful.png" alt-text="Screenshot of the validation grid." lightbox="./media/concepts-single-to-flexible/validation-successful.png":::
 
-The validation grid has the following columns
-- **Finding** - Represents the validation rules that are used to check readiness for migration.
-- **Finding Status** - Represents the result for each rule and can have any of the three values
+The validation grid has the 
+- **Validation details for instance** and **Validation details for databases** sections which represent the validation rules that are used to check readiness for migration. 
+- **Validation Status** - Represents the result for each rule and can have any of the three values
     - **Succeeded** - If no errors were found.  
     - **Failed** - If there are validation errors.
     - **Warning** - If there are validation warnings.
-- **Impacted Object** - Represents the object name for which the errors or warnings are raised. 
-- **Object Type** - This can have the value **Database** for database level validations and **Instance** for server level validations.
+- **Duration** - Time taken for the Validation operation.
+- **Start and End time** - Start and end time of the validation operation in UTC.
 
-The validation moves to **Validation Failed** state if there are any errors in the validation. Click on the **Finding** in the grid whose status is **Failed** and a fan-out pane gives the details and the corrective action you should take to avoid this error.
+The **Validation status** moves to **Failed** state if there are any errors in the validation. Click on the **Validation name** or **Database name** validation that has failed and a fan-out pane gives the details and the corrective action you should take to avoid this error.
 
 :::image type="content" source="./media/concepts-single-to-flexible/validation-failed.png" alt-text="Screenshot of the validation grid with failed status." lightbox="./media/concepts-single-to-flexible/validation-failed.png":::
 
@@ -199,16 +205,16 @@ In this option, validations are performed first before migration starts. After t
 - If validation has errors, the migration moves into a **Failed** state.
 - If validation completes without any error, the migration starts and the workflow will move into the sub state of **Migrating Data**. 
 
-You can see the results of validation under the **Validation** tab and monitor the migration under the **Migration** tab.
+You can see the results of **Validate and Migrate** once the operation is complete.
 
 :::image type="content" source="./media/concepts-single-to-flexible/validate-and-migrate-1.png" alt-text="Screenshot showing validations tab in details page." lightbox="./media/concepts-single-to-flexible/validate-and-migrate-1.png":::
 
-:::image type="content" source="./media/concepts-single-to-flexible/validate-and-migrate-2.png" alt-text="Screenshot showing migrations tab in details page." lightbox="./media/concepts-single-to-flexible/validate-and-migrate-2.png":::
-
 ### Online migration
 
 > [!NOTE]  
->  Support for **Online** migrations is currently available in UK South, South Africa North, UAE North, and all regions across Asia and Australia.
+>  Support for **Online** migrations is currently available in Central US, France Central, Germany West Central, North Central US, South Central US, North Europe, all West US regions, UK South, South Africa North, UAE North, and all regions across Asia and Australia. In other regions, Online migration can be enabled by the user at a subscription-level by registering for the **Online PostgreSQL migrations to Azure PostgreSQL Flexible server** preview feature as shown in the image.
+
+:::image type="content" source="./media/concepts-single-to-flexible/online-migration-feature-switch.png" alt-text="Screenshot of online PostgreSQL migrations to Azure PostgreSQL Flexible server." lightbox="./media/concepts-single-to-flexible/online-migration-feature-switch.png":::
 
 In case of both **Migrate** as well as **Validate and Migrate**, completion of the Online migration requires another step - a Cutover action is required from the user. After the copy/clone of the base data is complete, the migration moves to `WaitingForUserAction` state and `WaitingForCutoverTrigger` substate. In this state, user can trigger cutover from the portal by selecting the migration.