Your search did not match any results.
We suggest you try the following to help find what you’re looking for:
Reduce Costs with Hardware and Software Consolidation and Improve Reliability, Scalability, and Peformance with Oracle.
The Migrations Repository is a database schema that stores the meta_data collected and transformed in the migration process.
This step is used to capture a snapshot of the current state of your third-party database and is necessary to provide SQL Developer with a "point in time" view of your database. Once this step is complete, the Migration wizard works on the meta-data stored in its repository, instead of issuing queries against your live database.
The next step in the migration process is to convert the captured model of the database to an Oracle-specific model. The captured model contains data types, naming schemes etc. defined by your database vendor; this now must be converted to Oracle formats. Once the migration has completed, you can return the Captured Database Objects node and rerun the wizard from this point to convert some or all of the objects again.
The next step in the migration process is to translate the T-SQL objects - constraints, functions, procedures, triggers, views - to Oracle SQL objects. Once the migration has completed, you can return the Converted Database Objects node and rerun the Migration wizard to translate some or all of the objects again.
Once the conversion process has completed, SQL Developer has a model of what the converted database will look like. This is used to generate SQL scripts for the creation of the new Oracle Database schema(s) and to run these scripts.
The last step in the Migration Wizard is to move the data to the new database. Migrating the data is a process that copies the data from the third-party database to the new tables in the Oracle database. The Migration Wizard uses the same Oracle database connection required to run the scripts as it does to move the data.