Publish the schema by right-clicking the database from the Databases node in Azure SQL Database Metadata Explorer and selecting Synchronize with Database. To publish your schema and migrate your data: Migration involves two steps: publishing the schema and migrating the data.
Sql developer guide Offline#
This step gives you an opportunity to evaluate the source and target schemas offline and perform remediation before you publish the schema to SQL Database.Īfter you've assessed your databases and addressed any discrepancies, the next step is to run the migration process. Save the project locally for an offline schema remediation exercise. In the output pane, select Review results and review the errors in the Error List pane. Or, you can select your schema and then select the Convert Schema tab.Īfter the conversion finishes, compare and review the converted objects to the original objects to identify potential problems and address them based on the recommendations.Ĭompare the converted Transact-SQL text to the original stored procedures, and review the recommendations. In Oracle Metadata Explorer, right-click the Oracle schema and then select Convert Schema.
Enter authentication details, and select Connect. Select your target SQL Database instance from the drop-down list, or enter a new name, in which case a database will be created on the target server. In SQL Database, enter connection details to connect your database. Select the Connect to Azure SQL Database tab. Right-click the node, and then select Add statements. (Optional) Add dynamic or ad-hoc queries to statements. You can change the type mapping for each table by selecting the table in Oracle Metadata Explorer. In SSMA for Oracle, select Tools, and then select Project Settings. Validate the default data type mappings and change them based on requirements if necessary. The default location for the report is in the report folder within SSMAProjects.įor example, see drive:\\Documents\SSMAProjects\MyOracleMigration\report\report_2020_11_12T02_47_55\. You can also open the report in Excel to get an inventory of Oracle objects and the effort required to perform schema conversions. Review the HTML report to understand conversion statistics and any errors or warnings. Instead, you can select a database and then select the Create Report tab. In Oracle Metadata Explorer, right-click the Oracle schema you want to migrate and then select Create Report to generate an HTML report. Select the Oracle schemas you want to migrate. Enter values for Oracle connection details in the Connect to Oracle dialog box. Then select Azure SQL Database as the migration target from the drop-down list and select OK. Select File, and then select New Project.Įnter a project name and a location to save your project. Assessīy using SSMA for Oracle, you can review database objects and data, assess databases for migration, migrate database objects to SQL Database, and then finally migrate data to the database. This part of the process involves conducting an inventory of the databases that you need to migrate, assessing those databases for potential migration issues or blockers, and then resolving any items you might have uncovered. Obtain the necessary permissions for SSMA for Oracle and provider.Īfter you've met the prerequisites, you're ready to discover the topology of your environment and assess the feasibility of your Azure cloud migration. Verify that your source environment is supported. Prerequisitesīefore you begin migrating your Oracle schema to SQL Database: This guide teaches you to migrate your Oracle schemas to Azure SQL Database by using SQL Server Migration Assistant for Oracle (SSMA for Oracle).įor other migration guides, see Azure Database Migration Guides.
0 kommentar(er)
