Lokasi ngalangkungan proxy:   [ UP ]  
[Ngawartoskeun bug]   [Panyetelan cookie]                
Skip to content

Commit a23de25

Browse files
committed
Update database-migration-assessment-for-oracle-extension.md
1 parent a399f20 commit a23de25

1 file changed

Lines changed: 14 additions & 3 deletions

File tree

docs/azure-data-studio/extensions/database-migration-assessment-for-oracle-extension.md

Lines changed: 14 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ There are few extension settings that can be configured after installing the ext
4949
:::image type="content" source="media/database-migration-assessment-for-oracle-extension/dmaof-extension-settings-edit.png" alt-text="extension properties settings":::
5050

5151
>[!Note]
52-
> To perform Oracle to PostgreSQL assessment, Oracle client home path or Ora2pg installation path are mandatory parameters.
52+
> To perform Oracle to PostgreSQL code assessment, Oracle client home path and Ora2pg installation path are mandatory parameters.
5353
5454
## Run assessment
5555

@@ -89,7 +89,7 @@ Once the assessment extension installs, the next step is to connect to Oracle yo
8989
1. Enter your **Assessment setting**.
9090
1. In the **Target Platform** field, enter the destination migration database.Currently, it supports SQL and PostgreSQL as target.
9191
1. In the **Performance data collection** section, either select run performance data collection on Oracle database (connected) or Add AWR report.
92-
The recommendation is to use connected option if you are running this tool during peak or realistic load. Otherwise, provide the AWR reports generated in past for performance and sizing recommendation.
92+
The recommendation is to use connected option if you are running this tool during peak or realistic load. Otherwise, provide the AWR reports generated in past for performance and sizing recommendation.
9393
1. In the **Scale factor** field, enter the multiplier value.
9494
1. If the recommended SKU needs to consider other peak load, the scale factor multiplier should be greater than 1. Example: Burst Load, Seasonal usage, future capacity planning etc. Whereas when partial Oracle schema workload is considered migrated, then the multiplier should be less than 1.
9595

@@ -103,11 +103,15 @@ Once the assessment extension installs, the next step is to connect to Oracle yo
103103

104104
- Workload Assessment - In this assessment, the Oracle assessment module performs a lightweight discovery of the schema objects and categorize the schema complexity for migration to various categories with a high level estimated conversion hours.
105105

106-
- Code Assessment - The code assessment performs a deep assessment of the Oracle schema objects and then suggests an overall readiness of the code objects with ready, ready with conditions and not ready object types at granular level and its associated conversion hours with higher accuracy.
106+
- Code Assessment - The code assessment performs a deep assessment of the Oracle schema objects and then suggests an overall readiness of the code objects with ready, need review and not ready object types at granular level and its associated conversion hours with higher accuracy.
107107

108108
>[!Note]
109109
> For code assessment, the extension uses open source Ora2pg schema convertor.
110110
111+
If Oracle client and\or Ora2pg is not installed in the Azure data studio tool machine, either manually install them or use the script available here. - [Ora2pg installation script](https://github.com/microsoft/OrcasNinjaTeam/tree/master/ora2pg-install)
112+
113+
If Oracle client and Ora2pg is installed, ensure that the Oracle client home path and Ora2pg installation path is updated in the extension settings.
114+
111115
10. Now, you see the new assessment in the last five assessments section.
112116

113117
:::image type="content" source="media/database-migration-assessment-for-oracle-extension/dmafo-demo.png" alt-text="name the assessment demo":::
@@ -155,6 +159,13 @@ The code compatibility provides a summary of schema objects that can be converte
155159

156160
:::image type="content" source="media/database-migration-assessment-for-oracle-extension/dmao-code-compatibility-pg.png" alt-text="code compatibility report":::
157161

162+
The report shows the total number of objects and conversion effort hours required for migrating code to database for Azure PostgreSQL. The graphical image provides the breakup for each schema object type such as tables, views,cluster etc. The effort are categorized as Ready - Automatically converted, Needs review and not ready - requires manual conversion.
163+
164+
There is a further drill down for not ready and need review section. It provides the list of remediation tasks and the effort hours for each task.
165+
166+
:::image type="content" source="media/database-migration-assessment-for-oracle-extension/dmao-remediation-pg.png" alt-text="remediation task":::
167+
168+
158169
The feature assessment provides the Oracle to Azure data target mapped features and the effort required for migrating those capabilities to Azure target.
159170

160171
:::image type="content" source="media/database-migration-assessment-for-oracle-extension/dmafo-mapped-assessment.png" alt-text="Mapped assessment":::

0 commit comments

Comments
 (0)