Merge pull request #200100 from hariramt/task/S2FUpdate

Updated images and naming convention for Single to Flexible migration tool

Author: v-ccolin

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

@@ -13,17 +13,17 @@ ms.custom: "mvc, references_regions"
 # Migrate from Azure Database for PostgreSQL Single Server to Flexible Server (Preview)
 
 >[!NOTE]
-> Single Server to Flexible Server migration feature is in public preview.
+> Single Server to Flexible Server migration tool is in public preview.
 
-Azure Database for PostgreSQL Flexible Server provides zone redundant high availability, control over price, and control over maintenance window.  Single to Flexible Server Migration feature enables customers to migrate their databases from Single server to Flexible. See this [documentation](../flexible-server/concepts-compare-single-server-flexible-server.md) to understand the differences between Single and Flexible servers. Customers can initiate migrations for multiple servers and databases in a repeatable fashion using this migration feature. This feature automates most of the steps needed to do the migration and thus making the migration journey across Azure platforms as seamless as possible. The feature is provided free of cost for customers.
+Azure Database for PostgreSQL Flexible Server provides zone redundant high availability, control over price, and control over maintenance window.  Single to Flexible Server Migration tool enables customers to migrate their databases from Single server to Flexible. See this [documentation](../flexible-server/concepts-compare-single-server-flexible-server.md) to understand the differences between Single and Flexible servers. Customers can initiate migrations for multiple servers and databases in a repeatable fashion using this migration tool. This tool automates most of the steps needed to do the migration and thus making the migration journey across Azure platforms as seamless as possible. The tool is provided free of cost for customers.
 
 Single to Flexible server migration is enabled in **Preview** in  Australia Southeast, Canada Central, Canada East, East Asia, North Central US, South Central US, Switzerland North, UAE North, UK South, UK West, West US, and Central US.
 
 ## Overview
 
-Single to Flexible server migration feature provides an inline experience to migrate databases from Single Server (source) to Flexible Server (target).
+Single to Flexible server migration tool provides an inline experience to migrate databases from Single Server (source) to Flexible Server (target).
 
-You choose the source server and can select up to **8** databases from it. This limitation is per migration task. The migration feature automates the following steps:
+You choose the source server and can select up to **8** databases from it. This limitation is per migration task. The migration tool automates the following steps:
 
 1. Creates the migration infrastructure in the region of the target flexible server
 2. Creates public IP address and attaches it to the migration infrastructure
@@ -34,7 +34,7 @@ You choose the source server and can select up to **8** databases from it. This
 7. Creates databases with the same name on the target Flexible server
 8. Migrates data from source to target
 
-Following is the flow diagram for Single to Flexible migration feature.
+Following is the flow diagram for Single to Flexible migration tool.
 :::image type="content" source="./media/concepts-single-to-flexible/concepts-flow-diagram.png" alt-text="Diagram that shows Single to Flexible Server migration." lightbox="./media/concepts-single-to-flexible/concepts-flow-diagram.png":::
 
 **Steps:**
@@ -44,7 +44,7 @@ Following is the flow diagram for Single to Flexible migration feature.
 4. Initiates migration – (4a) Initial dump/restore (online & offline) (4b) streaming the changes (online only)
 5. Cutover to the target
 
-The migration feature is exposed through **Azure Portal** and via easy-to-use **Azure CLI** commands. It allows you to create migrations, list migrations, display migration details, modify the state of the migration, and delete   migrations
+The migration tool is exposed through **Azure Portal** and via easy-to-use **Azure CLI** commands. It allows you to create migrations, list migrations, display migration details, modify the state of the migration, and delete   migrations
 
 ## Migration modes comparison
 
@@ -93,9 +93,9 @@ Based on the above differences, pick the mode that best works for your workloads
 
 ### Pre-requisites
 
-Follow the steps provided in this section before you get started with the single to flexible server migration feature.
+Follow the steps provided in this section before you get started with the single to flexible server migration tool.
 
-- **Target Server Creation** - You need to create the target PostgreSQL flexible server before using the migration feature. Use the creation [QuickStart guide](../flexible-server/quickstart-create-server-portal.md) to create one.
+- **Target Server Creation** - You need to create the target PostgreSQL flexible server before using the migration tool. Use the creation [QuickStart guide](../flexible-server/quickstart-create-server-portal.md) to create one.
 
 - **Source Server pre-requisites** - You must [enable logical replication](./concepts-logical.md) on the source server.
 
@@ -104,7 +104,7 @@ Follow the steps provided in this section before you get started with the single
 >[!NOTE]
 > Enabling logical replication will require a server reboot for the change to take effect.
 
-- **Azure Active Directory App set up** - It is a critical component of the migration feature. Azure AD App helps with role-based access control as the migration feature needs access to both the source and target servers. See [How to setup and configure Azure AD App](./how-to-setup-azure-ad-app-portal.md) for step-by-step process.
+- **Azure Active Directory App set up** - It is a critical component of the migration tool. Azure AD App helps with role-based access control as the migration tool needs access to both the source and target servers. See [How to setup and configure Azure AD App](./how-to-setup-azure-ad-app-portal.md) for step-by-step process.
 
 ### Data and schema migration
 
@@ -131,7 +131,7 @@ Once all these pre-requisites are taken care of, you can do the migration. This
 
 ### Size limitations
 
-- Databases of sizes up to 1TB can be migrated using this feature. To migrate larger databases or heavy write workloads, reach out to your account team or reach us @ [email protected].
+- Databases of sizes up to 1TB can be migrated using this tool. To migrate larger databases or heavy write workloads, reach out to your account team or reach us @ [email protected].
 
 - In one migration attempt, you can migrate up to eight user databases from a single server to flexible server. In case you have more databases to migrate, you can create multiple migrations between the same single and flexible servers.
 
@@ -143,7 +143,7 @@ Once all these pre-requisites are taken care of, you can do the migration. This
 
 ### Replication limitations
 
-- Single to Flexible Server migration feature uses logical decoding feature of PostgreSQL to perform the online migration and it comes with the following limitations. See PostgreSQL documentation for [logical replication limitations](https://www.postgresql.org/docs/10/logical-replication-restrictions.html).
+- Single to Flexible Server migration tool uses logical decoding feature of PostgreSQL to perform the online migration and it comes with the following limitations. See PostgreSQL documentation for [logical replication limitations](https://www.postgresql.org/docs/10/logical-replication-restrictions.html).
   - **DDL commands** are not replicated.
   - **Sequence** data is not replicated.
   - **Truncate** commands are not replicated.(**Workaround**: use DELETE instead of TRUNCATE. To avoid accidental TRUNCATE invocations, you can revoke the TRUNCATE privilege from tables)
@@ -154,15 +154,15 @@ Once all these pre-requisites are taken care of, you can do the migration. This
 
 ### Other limitations
 
-- The migration feature migrates only data and schema of the single server databases to flexible server. It does not migrate other features such as server parameters, connection security details, firewall rules, users, roles and permissions. In other words, everything except data and schema must be manually configured in the target flexible server.
+- The migration tool migrates only data and schema of the single server databases to flexible server. It does not migrate other features such as server parameters, connection security details, firewall rules, users, roles and permissions. In other words, everything except data and schema must be manually configured in the target flexible server.
 
 - It does not validate the data in flexible server post migration. The customers must manually do this.
 
 - The migration tool only migrates user databases including Postgres database and not system/maintenance databases.
 
-- For failed migrations, there is no option to retry the same migration task. A new migration task with a unique name can to be created.
+- For failed migrations, there is no option to retry the same migration task. A new migration task with a unique name has to be created.
 
-- The migration feature does not include assessment of your single server. 
+- The migration tool does not include assessment of your single server. 
 
 ## Best practices
 

articles/postgresql/single-server/how-to-migrate-single-to-flexible-cli.md

@@ -12,9 +12,9 @@ ms.date: 05/09/2022
 # Migrate Single Server to Flexible Server PostgreSQL using Azure CLI
 
 >[!NOTE]
-> Single Server to Flexible Server migration feature is in public preview.
+> Single Server to Flexible Server migration tool is in public preview.
 
-This quick start article shows you how to use Single to Flexible Server migration feature to migrate databases from Azure database for PostgreSQL Single server to Flexible server.
+This quick start article shows you how to use Single to Flexible Server migration tool to migrate databases from Azure database for PostgreSQL Single server to Flexible server.
 
 ## Before you begin
 
@@ -38,11 +38,11 @@ This quick start article shows you how to use Single to Flexible Server migratio
       ```bash
       az login
       ```
-4. Take care of the pre-requisites listed in this [**document**](./concepts-single-to-flexible.md#pre-requisites) which are necessary to get started with the Single to Flexible migration feature.
+4. Take care of the pre-requisites listed in this [**document**](./concepts-single-to-flexible.md#pre-requisites) which are necessary to get started with the Single to Flexible migration tool.
 
 ## Migration CLI commands
 
-Single to Flexible Server migration feature comes with a list of easy-to-use CLI commands to do migration-related tasks. All the CLI commands start with  **az postgres flexible-server migration**. You can use the **help** parameter to help you with understanding the various options associated with a command and in framing the right syntax for the same.
+Single to Flexible Server migration tool comes with a list of easy-to-use CLI commands to do migration-related tasks. All the CLI commands start with  **az postgres flexible-server migration**. You can use the **help** parameter to help you with understanding the various options associated with a command and in framing the right syntax for the same.
 
 ```azurecli-interactive
 az postgres flexible-server migration --help
@@ -92,7 +92,7 @@ az postgres flexible-server migration create --subscription 5c5037e5-d3f1-4e7b-b
 
 The **migration-name** argument used in **create migration** command will be used in other CLI commands such as **update, delete, show** to uniquely identify the migration attempt and to perform the corresponding actions.
 
-The migration feature offers online and offline mode of migration. To know more about the migration modes and their differences, visit this [link](./concepts-single-to-flexible.md)
+The migration tool offers online and offline mode of migration. To know more about the migration modes and their differences, visit this [link](./concepts-single-to-flexible.md)
 
 Create a migration between a source and target server with a migration mode of your choice. The **create** command needs a JSON file to be passed as part of its **properties** argument.
 
@@ -149,10 +149,10 @@ Create migration parameters:
 | **SourceDBServerFullyQualifiedDomainName** | optional |  Used when a custom DNS server is used for name resolution for a virtual network. The FQDN of the single server as per the custom DNS server should be provided for this property. |
 | **TargetDBServerFullyQualifiedDomainName** | optional |  Used when a custom DNS server is used for name resolution inside a virtual network. The FQDN of the flexible server as per the custom DNS server should be provided for this property. <br> **_SourceDBServerFullyQualifiedDomainName_**, **_TargetDBServerFullyQualifiedDomainName_** should be included as a part of the JSON only in the rare scenario of a custom DNS server being used for name resolution instead of Azure provided DNS. Otherwise, these parameters should not be included as a part of the JSON file. |
 | **SecretParameters** | Required | Passwords for admin user for both single server and flexible server along with the Azure AD app credentials. They help to authenticate against the source and target servers and help in checking proper authorization access to the resources.
-| **MigrationResourceGroup** | optional | This section consists of two properties. <br> **ResourceID (optional)** : The migration infrastructure and other network infrastructure components are created to migrate data and schema from the source to target. By default, all the components created by this feature are provisioned under the resource group of the target server. If you wish to deploy them under a different resource group, then you can assign the resource ID of that resource group to this property. <br> **SubnetResourceID (optional)** : In case if your source has public access turned OFF or if your target server is deployed inside a VNet, then specify a subnet under which migration infrastructure needs to be created so that it can connect to both source and target servers. |
+| **MigrationResourceGroup** | optional | This section consists of two properties. <br> **ResourceID (optional)** : The migration infrastructure and other network infrastructure components are created to migrate data and schema from the source to target. By default, all the components created by this tool are provisioned under the resource group of the target server. If you wish to deploy them under a different resource group, then you can assign the resource ID of that resource group to this property. <br> **SubnetResourceID (optional)** : In case if your source has public access turned OFF or if your target server is deployed inside a VNet, then specify a subnet under which migration infrastructure needs to be created so that it can connect to both source and target servers. |
 | **DBsToMigrate** | Required | Specify the list of databases you want to migrate to the flexible server. You can include a maximum of 8 database names at a time. |
 | **SetupLogicalReplicationOnSourceDBIfNeeded** | Optional | Logical replication can be enabled on the source server automatically by setting this property to **true**. This change in the server settings requires a server restart with a downtime of few minutes (~ 2-3 mins). |
-| **OverwriteDBsinTarget** | Optional | If the target server happens to have an existing database with the same name as the one you are trying to migrate, the migration will pause until you acknowledge that overwrites in the target DBs are allowed. This pause can be avoided by giving the migration feature, permission to automatically overwrite databases by setting the value of this property to **true** |
+| **OverwriteDBsinTarget** | Optional | If the target server happens to have an existing database with the same name as the one you are trying to migrate, the migration will pause until you acknowledge that overwrites in the target DBs are allowed. This pause can be avoided by giving the migration tool, permission to automatically overwrite databases by setting the value of this property to **true** |
 
 ### Mode of migrations