Merge pull request #176616 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to master to sync with https://github.com/MicrosoftDocs/azure-docs (branch master)

Author: huypub

articles/cosmos-db/sql/performance-testing.md

@@ -22,7 +22,7 @@ After reading this article, you'll be able to answer the following questions:
 * Where can I find a sample .NET client application for performance testing of Azure Cosmos DB? 
 * How do I achieve high throughput levels with Azure Cosmos DB from my client application?
 
-To get started with code, download the project from [Azure Cosmos DB performance testing sample](https://github.com/Azure/azure-cosmos-dotnet-v2/tree/master/samples/documentdb-benchmark). 
+To get started with code, download the project from [Azure Cosmos DB performance testing sample](https://github.com/Azure/azure-cosmos-dotnet-v3/tree/master/Microsoft.Azure.Cosmos.Samples/Tools/Benchmark). 
 
 > [!NOTE]
 > The goal of this application is to demonstrate how to get the best performance from Azure Cosmos DB with a small number of client machines. The goal of the sample is not to achieve the peak throughput capacity of Azure Cosmos DB (which can scale without any limits).
@@ -32,7 +32,7 @@ If you're looking for client-side configuration options to improve Azure Cosmos
 ## Run the performance testing application
 The quickest way to get started is to compile and run the .NET sample, as described in the following steps. You can also review the source code and implement similar configurations on your own client applications.
 
-**Step 1:** Download the project from [Azure Cosmos DB performance testing sample](https://github.com/Azure/azure-cosmos-dotnet-v2/tree/master/samples/documentdb-benchmark), or fork the GitHub repository.
+**Step 1:** Download the project from [Azure Cosmos DB performance testing sample](https://github.com/Azure/azure-cosmos-dotnet-v3/tree/master/Microsoft.Azure.Cosmos.Samples/Tools/Benchmark), or fork the GitHub repository.
 
 **Step 2:** Modify the settings for EndpointUrl, AuthorizationKey, CollectionThroughput, and DocumentTemplate (optional) in App.config.
 
@@ -92,7 +92,7 @@ After you have the app running, you can try different [indexing policies](../ind
 
 In this article, we looked at how you can perform performance and scale testing with Azure Cosmos DB by using a .NET console app. For more information, see the following articles:
 
-* [Azure Cosmos DB performance testing sample](https://github.com/Azure/azure-cosmos-dotnet-v2/tree/master/samples/documentdb-benchmark)
+* [Azure Cosmos DB performance testing sample](https://github.com/Azure/azure-cosmos-dotnet-v3/tree/master/Microsoft.Azure.Cosmos.Samples/Tools/Benchmark)
 * [Client configuration options to improve Azure Cosmos DB performance](performance-tips.md)
 * [Server-side partitioning in Azure Cosmos DB](../partitioning-overview.md)
 * Trying to do capacity planning for a migration to Azure Cosmos DB? You can use information about your existing database cluster for capacity planning.

articles/data-factory/pricing-concepts.md

@@ -46,10 +46,10 @@ To accomplish the scenario, you need to create a pipeline with the following ite
 **Total Scenario pricing: $0.16811**
 
 - Data Factory Operations = **$0.0001**
-  - Read/Write = 10\*00001 = $0.0001 [1 R/W = $0.50/50000 = 0.00001]
-  - Monitoring  = 2\*000005 = $0.00001 [1 Monitoring = $0.25/50000 = 0.000005]
+  - Read/Write = 10\*0.00001 = $0.0001 [1 R/W = $0.50/50000 = 0.00001]
+  - Monitoring  = 2\*0.000005 = $0.00001 [1 Monitoring = $0.25/50000 = 0.000005]
 - Pipeline Orchestration & Execution = **$0.168**
-  - Activity Runs = 001\*2 = 0.002 [1 run = $1/1000 = 0.001]
+  - Activity Runs = 0.001\*2 = $0.002 [1 run = $1/1000 = 0.001]
   - Data Movement Activities = $0.166 (Prorated for 10 minutes of execution time. $0.25/hour on Azure Integration Runtime)
 
 ## Copy data and transform with Azure Databricks hourly
@@ -78,10 +78,10 @@ To accomplish the scenario, you need to create a pipeline with the following ite
 **Total Scenario pricing: $0.16916**
 
 - Data Factory Operations = **$0.00012**
-  - Read/Write = 11\*00001 = $0.00011 [1 R/W = $0.50/50000 = 0.00001]
-  - Monitoring  = 3\*000005 = $0.00001 [1 Monitoring = $0.25/50000 = 0.000005]
+  - Read/Write = 11\*0.00001 = $0.00011 [1 R/W = $0.50/50000 = 0.00001]
+  - Monitoring  = 3\*0.000005 = $0.00001 [1 Monitoring = $0.25/50000 = 0.000005]
 - Pipeline Orchestration & Execution = **$0.16904**
-  - Activity Runs = 001\*3 = 0.003 [1 run = $1/1000 = 0.001]
+  - Activity Runs = 0.001\*3 = $0.003 [1 run = $1/1000 = 0.001]
   - Data Movement Activities = $0.166 (Prorated for 10 minutes of execution time. $0.25/hour on Azure Integration Runtime)
   - External Pipeline Activity = $0.000041 (Prorated for 10 minutes of execution time. $0.00025/hour on Azure Integration Runtime)
 
@@ -113,10 +113,10 @@ To accomplish the scenario, you need to create a pipeline with the following ite
 **Total Scenario pricing: $0.17020**
 
 - Data Factory Operations = **$0.00013**
-  - Read/Write = 11\*00001 = $0.00011 [1 R/W = $0.50/50000 = 0.00001]
-  - Monitoring  = 4\*000005 = $0.00002 [1 Monitoring = $0.25/50000 = 0.000005]
+  - Read/Write = 11\*0.00001 = $0.00011 [1 R/W = $0.50/50000 = 0.00001]
+  - Monitoring  = 4\*0.000005 = $0.00002 [1 Monitoring = $0.25/50000 = 0.000005]
 - Pipeline Orchestration & Execution = **$0.17007**
-  - Activity Runs = 001\*4 = 0.004 [1 run = $1/1000 = 0.001]
+  - Activity Runs = 0.001\*4 = $0.004 [1 run = $1/1000 = 0.001]
   - Data Movement Activities = $0.166 (Prorated for 10 minutes of execution time. $0.25/hour on Azure Integration Runtime)
   - Pipeline Activity = $0.00003 (Prorated for 1 minute of execution time. $0.002/hour on Azure Integration Runtime)
   - External Pipeline Activity = $0.000041 (Prorated for 10 minutes of execution time. $0.00025/hour on Azure Integration Runtime)
@@ -168,10 +168,10 @@ To accomplish the scenario, you need to create a pipeline with the following ite
 **Total Scenario pricing: $1.4631**
 
 - Data Factory Operations = **$0.0001**
-  - Read/Write = 10\*00001 = $0.0001 [1 R/W = $0.50/50000 = 0.00001]
-  - Monitoring  = 2\*000005 = $0.00001 [1 Monitoring = $0.25/50000 = 0.000005]
+  - Read/Write = 10\*0.00001 = $0.0001 [1 R/W = $0.50/50000 = 0.00001]
+  - Monitoring  = 2\*0.000005 = $0.00001 [1 Monitoring = $0.25/50000 = 0.000005]
 - Pipeline Orchestration & Execution = **$1.463**
-  - Activity Runs = 001\*2 = 0.002 [1 run = $1/1000 = 0.001]
+  - Activity Runs = 0.001\*2 = $0.002 [1 run = $1/1000 = 0.001]
   - Data Flow Activities = $1.461 prorated for 20 minutes (10 mins execution time + 10 mins TTL). $0.274/hour on Azure Integration Runtime with 16 cores general compute
 
 ## Data integration in Azure Data Factory Managed VNET
@@ -199,10 +199,10 @@ To accomplish the scenario, you need to create two pipelines with the following
 **Total Scenario pricing: $1.45523**
 
 - Data Factory Operations = $0.00023
-  - Read/Write = 20*00001 = $0.0002 [1 R/W = $0.50/50000 = 0.00001]
-  - Monitoring = 6*000005 = $0.00003 [1 Monitoring = $0.25/50000 = 0.000005]
+  - Read/Write = 20*0.00001 = $0.0002 [1 R/W = $0.50/50000 = 0.00001]
+  - Monitoring = 6*0.000005 = $0.00003 [1 Monitoring = $0.25/50000 = 0.000005]
 - Pipeline Orchestration & Execution = $1.455
-  - Activity Runs = 0.001*6 = 0.006 [1 run = $1/1000 = 0.001]
+  - Activity Runs = 0.001*6 = $0.006 [1 run = $1/1000 = 0.001]
   - Data Movement Activities = $0.333 (Prorated for 10 minutes of execution time. $0.25/hour on Azure Integration Runtime)
   - Pipeline Activity = $1.116 (Prorated for 7 minutes of execution time plus 60 minutes TTL. $1/hour on Azure Integration Runtime)
 

articles/dms/tutorial-postgresql-azure-postgresql-online-portal.md

@@ -38,9 +38,9 @@ In this tutorial, you learn how to:
 
 To complete this tutorial, you need to:
 
-* Download and install [PostgreSQL community edition](https://www.postgresql.org/download/) 9.4, 9.5, 9.6, or 10. The source PostgreSQL Server version must be 9.4, 9.5, 9.6, 10, 11 or 12. For more information, see the article [Supported PostgreSQL Database Versions](../postgresql/concepts-supported-versions.md).
+* Download and install [PostgreSQL community edition](https://www.postgresql.org/download/) 9.4, 9.5, 9.6, or 10. The source PostgreSQL Server version must be 9.4, 9.5, 9.6, 10, 11, 12, or 13. For more information, see [Supported PostgreSQL database versions](../postgresql/concepts-supported-versions.md).
 
-    Also note that the target Azure Database for PostgreSQL version must be equal to or later than the on-premises PostgreSQL version. For example, PostgreSQL 9.6 can migrate to Azure Database for PostgreSQL 9.6, 10, or 11, but not to Azure Database for PostgreSQL 9.5. Migrations to PostgreSQL 13+ are not supported at this time. 
+    Also note that the target Azure Database for PostgreSQL version must be equal to or later than the on-premises PostgreSQL version. For example, PostgreSQL 9.6 can migrate to Azure Database for PostgreSQL 9.6, 10, or 11, but not to Azure Database for PostgreSQL 9.5. 
 
 * [Create an Azure Database for PostgreSQL server](../postgresql/quickstart-create-server-database-portal.md) or [Create an Azure Database for PostgreSQL - Hyperscale (Citus) server](../postgresql/quickstart-create-hyperscale-portal.md).
 * Create a Microsoft Azure Virtual Network for Azure Database Migration Service by using the Azure Resource Manager deployment model, which provides site-to-site connectivity to your on-premises source servers by using either [ExpressRoute](../expressroute/expressroute-introduction.md) or [VPN](../vpn-gateway/vpn-gateway-about-vpngateways.md). For more information about creating a virtual network, see the [Virtual Network Documentation](../virtual-network/index.yml), and especially the quickstart articles with step-by-step details.