Migrate the Data
- Online Data Move: You can create a connection from within Oracle SQL Developer to your Microsoft SQL Server source database and migrate the data.
- Offline Data Move: You can export the data from Microsoft SQL Server. SQL Developer
will create a series of BCP and
sqlldr
files that you can run from a batch file.
Online data moves are suitable for small data sets, whereas offline data moves are useful for moving large volumes of data. Furthermore, in cases of large volumes of data, it is recommended to use Oracle Cloud Infrastructure File Storage to help overall performance of data movement during migration process.
Migrate the Data Offline
During the capture process, the offline data move script would have been
generated and the data would have been extracted into the project output directory named
datamove
. The execution of these scripts is what migrates the data from
sql
server windows host machine to Oracle Autonomous Database.
datamove
directory should look like
this:Wkdir
projectName
datamove
YYYY-MM-DD_HH-MI-SS
AdventureWorks
Inside the AdventureWorks directory, you should see six subfolders that correspond to all users under SQL Server AdventureWorks database.
You should see the following directories in the AdventureWorks folder:
- ADVENTUREWORKS
- SALES_ADVENTUREWORKS
- PERSON_ADVENTUREWORKS
- PURCHASING_ADVENTUREWORKS
- HUMANRESOURCES_ADVENTUREWORKS
- PRODUCTION_ADVENTUREWORKS
You should see the following files in the AdventureWorks folder:
MicrosoftSQLServer_data.bat
MicrosoftSQLServer_data.sh
oracle_external.bat
oracle_external.sh
oracle_loader.bat
oracle_loader.sh
The script MicrosoftSqlServer_data.bat
is the master
Windows system batch script that calls other batch scripts created within each of
the schema directories. Here is sample execution:
Test the Migration
Depending on the complexity of the database being migrated, a large part of the migration project might be testing.
Oracle does not provide any tools that can automatically validate a migrated database for you. This phase of the migration should be planned and taken into account before the migration begins. The following should be part of your project plan:
- Verify the database structure.
- Verify the database security.
- Verify the data.
- Verify the logical correctness of views.
- Test the applications.