pg tweaks

Author: HJToland3

articles/dms/known-issues-azure-postgresql-online.md

@@ -76,9 +76,9 @@ Known issues and limitations associated with online migrations from PostgreSQL t
 
 ## Datatype limitations
 
-- **Limitation**: If there's no primary key on tables, changes may not be synced to the target database.
+  **Limitation**: If there's no primary key on tables, changes may not be synced to the target database.
 
-    **Workaround**: Temporarily set a primary key for the table for migration to continue. You can remove the primary key after data migration is complete.
+  **Workaround**: Temporarily set a primary key for the table for migration to continue. You can remove the primary key after data migration is complete.
 
 ## Limitations when migrating online from AWS RDS PostgreSQL
 
@@ -92,11 +92,13 @@ When you try to perform an online migration from AWS RDS PostgreSQL to Azure Dat
 - **Error**: Target database '{database}' has '{number of tables}' tables where as source database '{database}' has '{number of tables}' tables. The number of tables on source and target databases should match.
 
   **Limitation**: This error occurs when the number of tables is different between the source and target databases.
+
   **Workaround**: Ensure that the schema on the target matches schema on the source. For detail on migrating schema, refer to the [Azure PostgreSQL online migration documentation](https://docs.microsoft.com/azure/dms/tutorial-postgresql-azure-postgresql-online#migrate-the-sample-schema).
 
 - **Error:** The source database {database} is empty.
 
   **Limitation**: This error occurs when the source database is empty. It is most likely because you have selected the wrong database as source.
+
   **Workaround**: Double-check the source database you selected for migration, and then try again.
 
 - **Error:** The target database {database} is empty. Please migrate the schema.

articles/dms/media/tutorial-postgresql-to-azure-postgresql-online-portal/dms-instance-search.png

@@ -198,22 +198,18 @@ After the service is created, locate it within the Azure portal, open it, and th
 
       ![Locate all instances of Azure Database Migration Service](media/tutorial-postgresql-to-azure-postgresql-online-portal/dms-search.png)
 
-2. On the **Azure Database Migration Services** screen, search for the name of Azure Database Migration Service instance that you created, and then select the instance.
+2. On the **Azure Database Migration Services** screen, search for the name of Azure Database Migration Service instance that you created, select the instance, and then select + **New Migration Project**.
 
-     ![Locate your instance of Azure Database Migration Service](media/tutorial-postgresql-to-azure-postgresql-online-portal/dms-instance-search.png)
+3. On the **New migration project** screen, specify a name for the project, in the **Source server type** text box, select **PostgresSQL**, in the **Target server type** text box, select **Azure Database for PostgreSQL**.
 
-3. Select + **New Migration Project**.
-
-4. On the **New migration project** screen, specify a name for the project, in the **Source server type** text box, select **PostgresSQL**, in the **Target server type** text box, select **Azure Database for PostgreSQL**.
-
-5. In the **Choose type of activity** section, select **Online data migration**.
+4. In the **Choose type of activity** section, select **Online data migration**.
 
     ![Create Azure Database Migration Service project](media/tutorial-postgresql-to-azure-postgresql-online-portal/dms-create-project.png)
 
     > [!NOTE]
     > Alternately, you can choose **Create project only** to create the migration project now and execute the migration later.
 
-6. Select **Save**, note the requirements to successfully use Azure Database Migration Service to migrate data, and then select **Create and run activity**.
+5. Select **Save**, note the requirements to successfully use Azure Database Migration Service to migrate data, and then select **Create and run activity**.
 
 ## Specify source details
 

articles/dms/media/tutorial-postgresql-to-azure-postgresql-online-portal/portal-marketplace.png

@@ -372,7 +372,7 @@ To complete all the database objects like table schemas, indexes and stored proc
 
 In the output file, there are several parameters that indicate progress of migration. For example, see the output file below:
 
-    ```
+  ```
     "output": [									Database Level
           {
             "appliedChanges": 0,		//Total incremental sync applied after full load
@@ -447,7 +447,7 @@ In the output file, there are several parameters that indicate progress of migra
       },
       "resourceGroup": "PostgresDemo",
       "type": "Microsoft.DataMigration/services/projects/tasks"
-    ```
+  ```
 
 ## Cutover migration task
 

articles/dms/media/tutorial-rds-postgresql-server-azure-db-for-postgresql-online/dms-instance-search.png

@@ -59,9 +59,13 @@ To complete this tutorial, you need to:
 1. To create a new parameter group, follow the instructions provided by AWS in the article [Working with DB Parameter Groups](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_WorkingWithParamGroups.html).
 2. Use the master user name to connect to the source from Azure Database Migration Service. If you use an account other than the master user account, the account must have the rds_superuser role and the rds_replication role. The rds_replication role grants permissions to manage logical slots and to stream data using logical slots.
 3. Create a new parameter group with the following configuration:
+
     a. Set the rds.logical_replication parameter in your DB parameter group to 1.
+
     b. max_wal_senders =[number of concurrent tasks] - The max_wal_senders parameter sets the number of concurrent tasks that can run, recommend 10 tasks.
+
     c. max_replication_slots – = [number of slots], recommend set to five slots.
+
 4. Associate the parameter group you created to the RDS PostgreSQL instance.
 
 ## Migrate the schema
@@ -183,13 +187,9 @@ After the service is created, locate it within the Azure portal, open it, and th
 
       ![Locate all instances of the Azure Database Migration Service](media/tutorial-rds-postgresql-server-azure-db-for-postgresql-online/dms-search.png)
 
-2. On the **Azure Database Migration Services** screen, search for the name of the Azure Database Migration Service instance that you created, and then select the instance.
-
-     ![Locate your instance of the Azure Database Migration Service](media/tutorial-rds-postgresql-server-azure-db-for-postgresql-online/dms-instance-search.png)
-
-3. Select + **New Migration Project**.
-4. On the **New migration project** screen, specify a name for the project, in the **Source server type** text box, select **AWS RDS for PostgreSQL**, and then in the **Target server type** text box, select **Azure Database for PostgreSQL**.
-5. In the **Choose type of activity** section, select **Online data migration**.
+2. On the **Azure Database Migration Services** screen, search for the name of the Azure Database Migration Service instance that you created, select the instance, and then select + **New Migration Project**.
+3. On the **New migration project** screen, specify a name for the project, in the **Source server type** text box, select **AWS RDS for PostgreSQL**, and then in the **Target server type** text box, select **Azure Database for PostgreSQL**.
+4. In the **Choose type of activity** section, select **Online data migration**.
 
     > [!IMPORTANT]
     > Be sure to select **Online data migration**; offline migrations are not supported for this scenario.
@@ -199,9 +199,9 @@ After the service is created, locate it within the Azure portal, open it, and th
     > [!NOTE]
     > Alternately, you can choose **Create project only** to create the migration project now and execute the migration later.
 
-6. Select **Save**.
+5. Select **Save**.
 
-7. Select **Create and run activity** to create the project and run the migration activity.
+6. Select **Create and run activity** to create the project and run the migration activity.
 
     > [!NOTE]
     > Please make a note of the pre-requisites needed to set up online migration in the project creation blade.