This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Which stage of the Oracle to Azure Database for PostgreSQL schema conversion pipeline uses the Microsoft Foundry language model?
Source Oracle metadata extraction, where the tool reads schema objects from the Oracle data dictionary.
AI-powered transformation, where schema conversion agents translate Oracle DDL into PostgreSQL-compatible DDL.
Scratch-schema validation, where the tool applies generated DDL to the Azure Database for PostgreSQL flexible server.
You're configuring Oracle connectivity for a schema conversion project. The source Oracle environment uses native network encryption: the sqlnet.ora file sets SQLNET.ENCRYPTION_CLIENT to REQUIRED. What does the conversion tool do, and what must you prepare before starting the conversion?
sqlnet.ora
SQLNET.ENCRYPTION_CLIENT
REQUIRED
The tool uses thin client mode because Oracle 12.1 and later are supported, and no extra preparation is needed.
The tool switches to thick client mode automatically and requires Oracle Instant Client to be installed on the VS Code machine before you start the conversion.
The tool prompts you to select thin or thick mode manually in the Migration Wizard and works with either choice as long as Oracle is reachable.
After a conversion run, the customer summary report shows a 92% success percentage. Your project sponsor asks whether the converted schema is ready to deploy to production. How should you interpret this number?
The success percentage reflects how many objects converted automatically without manual intervention. It doesn't indicate production readiness; you resolve review tasks and independently validate the converted objects first.
A success percentage above 90% means the schema is production-ready and you can deploy it as-is.
The success percentage is the proportion of objects that passed scratch-schema validation, so only the remaining objects need review.
After running a schema conversion, the Schema Review pane shows five Mandatory tasks, twelve Recommended tasks, and three Optional tasks. You need to deploy the schema to a test environment for functional testing as soon as possible. What is the minimum set of review tasks you must resolve before deployment?
All twenty tasks, because unresolved review tasks indicate conversion failures and block any deployment.
The five Mandatory tasks, because they block deployment until resolved.
Only the Optional tasks, because Mandatory and Recommended tasks are handled automatically by GitHub Copilot agent mode.
You must answer all questions before checking your work.
Was this page helpful?
Need help with this topic?
Want to try using Ask Learn to clarify or guide you through this topic?