Skip to content

Commit 6f0bc80

Browse files
committed
pg updates
1 parent 636ea9c commit 6f0bc80

12 files changed

+21
-20
lines changed
52.9 KB
Loading
40.1 KB
Loading
40 KB
Loading
52.9 KB
Loading
35.9 KB
Loading
33 KB
Loading

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.service: dms
1111
ms.workload: data-services
1212
ms.custom: "seo-lt-2019"
1313
ms.topic: article
14-
ms.date: 02/13/2020
14+
ms.date: 02/17/2020
1515
---
1616

1717
# Tutorial: Migrate PostgreSQL to Azure DB for PostgreSQL online using DMS via the Azure portal
@@ -184,9 +184,9 @@ To complete all the database objects like table schemas, indexes and stored proc
184184
185185
For more information on costs and pricing tiers, see the [pricing page](https://aka.ms/dms-pricing).
186186
187-
![Configure Azure Database Migration Service instance settings](media/tutorial-postgresql-to-azure-postgresql-online-portal/dms-settings3.png)
187+
![Configure Azure Database Migration Service instance settings](media/tutorial-postgresql-to-azure-postgresql-online-portal/dms-settings4.png)
188188
189-
6. Select **Create** to create the service.
189+
6. Select **Review + create** to create the service.
190190
191191
Service creation will complete within about 10 to 15 minutes.
192192
@@ -274,7 +274,7 @@ After the initial Full load is completed, the databases are marked **Ready to cu
274274
275275
![Complete cutover screen](media/tutorial-postgresql-to-azure-postgresql-online-portal/dms-complete-cutover.png)
276276
277-
3. When the database migration status shows **Completed**, connect your applications to the new target instance of Hyperscale (Citus).
277+
3. When the database migration status shows **Completed**, connect your applications to the new target instance of Azure Database for PostgreSQL.
278278
279279
## Next steps
280280

0 commit comments

Comments
 (0)