7. From the Tools menu within Microsoft Access, select Database, then select Compact Database to compact the Microsoft Access database files
2.14 SQL Developer User Interface for Migration
If you are performing database migration, you need to use some migration-specific features in addition to those described in Section 1.2, "SQL Developer User Interface".
The user interface includes some additional navigator tabs and panes (Captured Models and Converted Models) and a Migration menu, and many smaller changes throughout the interface. Figure 2–3, "Main Window for a Database Migration" shows the SQL Developer main window with objects reflecting the migration of a Microsoft Access application named sales.mdb.
SQL Developer User Interface for Migration
Figure 2–3 Main Window for a Database Migration
In this figure:
SQL Developer User Interface for Migration
■ The Connections navigator shows three database connections: migration_
repository for a connection (to a user named MIGRATION) used for the migration repository, sales_access connected to a Microsoft Access database named sales.mdb, and sales_oracle connected to an Oracle user named SALES whose schema owns the migrated schema objects.
■ The Captured Models navigator shows one captured model, which was created using an XML file created by the exporter tool for Access applications. (If the source database is a type other than Microsoft Access, the procedure for creating the captured model is different: you can generate it directly from the source database connection.)
■ The Converted Models navigator shows one converted model, which is an Oracle representation of the source database. The converted model is created from the captured model, and the converted model is used to generate the schema objects that you can see using an Oracle database connection (sales_oracle in this figure).
2.14.1 Migration Menu
The Migration menu contains options related to migrating third-party databases to Oracle.
Quick Migrate: Displays a dialog box for performing a quick migration using many default values.
Repository Management: Enables you to create, delete, or truncate (remove all data from) a migration repository; select the current migration repository; and disconnect from the current migration repository (which deactivates the current repository but does not disconnect from the database).
Microsoft Access Exporter: Contains submenu items from which you specify the version of the exporter tool to use to create an XML file to be used for creating the captured model. You can also use the exporter tool to export table data. Specify the exporter tool version for the version of Access that is on your PC and that was used to create the .mdb file.
Migrate Data: Displays a dialog box for performing an online migration of table data from the source database to the Oracle schema.
Script Generation: Generate Oracle DDL displays DDL (data definition language) statements in a SQL Worksheet window, where you can then run the script to create the Oracle schema and schema objects; Generate Data Move Scripts displays a dialog box for specifying the location in which to create files for performing an offline migration of table data from the source database to the Oracle schema.
Capture Microsoft Access Exporter XML: Creates a captured model of a Microsoft Access database from the XML file created by the exporter tool.
MySQL, SQL Server, and Sybase Offline Capture: Create Database Capture Scripts specifies options for creating an offline capture properties (.ocp) file, which you can later load and run; Load Database Capture Script Output enables you to select a script to be loaded and run.
Script Generation: Generate Oracle DDL specifies the converted model for which to generate Oracle DDL and produces a SQL*Plus script file that you use for offline generation (that is, you can run the script to create the appropriate objects in the Oracle database); Generate Data Move Scripts specifies the converted model and the destination directory if you are performing offline data migration.
Translation Scratch Editor: Displays the translation scratch editor, which is explained in Section 2.14.5.
SQL Developer User Interface for Migration
2.14.2 Other Menus: Migration Items
The View menu has the following items related to database migration:
■ Captured Models: Displays the Captured Models navigator.
■ Converted Models: Displays the Converted Models navigator.
2.14.3 Migration Preferences
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 Section 1.13.10,
"Migration".
2.14.4 Migration Log Panes
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.
2.14.5 Using the Translation Scratch Editor
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 Migration, then Translation Scratch Editor. The scratch editor consists of two SQL Worksheet windows side by side, as shown in the following figure:
SQL Developer User Interface for Migration
To translate a statement to its Oracle equivalent, select the type of translation, enter the third-party SQL statement or statements, 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 Section 1.7, "Using the SQL Worksheet".
Note: For a Microsoft SQL Server or Sybase Adaptive Server connection, the worksheet does not support running T-SQL statements. It only supports SELECT, CREATE, INSERT, UPDATE, DELETE, and DROP statements.
3
3