Home > SQL Developer: Migrating Th... > SQL Developer User Interfac...
If you are performing database migration, you need to use some migration-specific features in addition to those described in SQL Developer User Interface. The user interface includes an additional navigator (Migration Projects), a Migration submenu under Tools, and many smaller changes throughout the interface. Figure: Main Window for a Database Migration shows the SQL Developer main window with objects reflecting the migration of a Sybase database. It also shows the Migration Submenu.
In this figure:
The Connections navigator shows a connection named sybase_15
, which is to the Sybase database to be migrated to Oracle. This connection name also appears in a drop-down control in the upper right area.
In the migration projects navigator, <repository-connection> after "Projects -" will be the actual connection name for the migration repository.
The migration project name is sybase_15_migr
.
Under the project name are trees (hierarchies) for Captured Database Objects and Converted Database Objects.
Note: As an alternative to using the SQL Developer graphical interface for migration tasks, you can use the command line, which is explained in Command-Line Interface for SQL Developer. |
Related Topics
SQL Developer: Migrating Third-Party Databases
The Migration submenu contains options related to migrating third-party databases to Oracle. To display the Migration submenu, click Tools, then Migration.
Migrate: Displays a wizard for performing an efficient migration. The wizard displays steps and options relevant to your specified migration.
Scan Application: Displays the Application Migration wizard.
Scratch Editor: Displays the translation scratch editor, which is explained in Using the Translation Scratch Editor.
Create Database Capture Scripts specifies options for creating script files, including an offline capture properties (.ocp) file, which you can later load and run.
Repository Management: Enables you to create (associate) or delete a migration repository, disconnect from the current repository (deactivates the current repository but does not disconnect from the database), or truncate (remove all data from) the repository.
The View menu has the following item related to database migration:
Migration Projects: Displays the Migration Projects navigator, which includes any captured models and converted models in the currently selected migration repository.
The SQL Developer user preferences window (displayed by clicking Tools, then Preferences) contains a Migration pane with several related subpanes, and a Translation pane with a Translation Preferences subpane.
For information about these preferences, click Help in the pane, or see Migration.
Migration Log: Contains errors, warnings, and informational messages relating to migration operations.
Logging Page: Contains an entry for each migrated-related operation.
Data Editor Log: Contains entries when data is being manipulated by SQL Developer. For example, the output of a Microsoft Excel import operation will be reported here as a series of INSERT statements.
You can use the translation scratch editor to enter third-party database SQL statements and have them translated to Oracle PL/SQL statements. You can specify translation from Microsoft SQL Server T-SQL to PL/SQL, from Sybase T-SQL to PL/SQL, or from Microsoft Access SQL to PL/SQL.
You can display the scratch editor by clicking Tools, then Migration, then Translation Scratch Editor. The scratch editor consists of two SQL Worksheet windows side by side, as shown in the following figure:
To translate a statement to its Oracle equivalent, select the type of translation, enter the third-party SQL statement or statements; select the specific translation from the Translator drop-down (for example, Access SQL to PL/SQL
) and optionally the applicable schema from the Captured Schema drop-down; then click the Translate (>>) icon to display the generated PL/SQL statement or statements.
SQL keywords are automatically highlighted.
The first time you save the contents of either worksheet window in the translation scratch editor, you are prompted for the file location and name. If you perform any subsequent Save operations (regardless of whether you have erased or changed the content of the window), the contents are saved to the same file. To save the contents to a different file, click File, then Save As.
For detailed information about the worksheet windows, see Using the SQL Worksheet.
Related Topics
SQL Developer: Migrating Third-Party Databases
Migration: Basic Options and Steps