After clicking OK on the
setup window, returning to the ODBC Data Source Administrator window shows that
the data source named Northwind is using the SQL Server driver. Click OK to
dismiss the window.
Now we are ready to make Migration Workbench work with SQL Server. If you do not already have it, you will need the plug-in for SQL Server 2000. Oracle Technology Network, at the time of this writing, was reorganizing their download area, so you may get a "page not found or DNS server error" when clicking on the link at http://www.oracle.com/technology/software/tech/migration/workbench/index.html.
If you encounter this error,
send an email to firstname.lastname@example.org
and ask to have the JAR file emailed to you (it is only 542KB in its compressed
state, and 575KB uncompressed). If you navigate to the download page directly,
you can skip the survey.
Once the plug-in is
extracted and placed in the plugins directory of your OWMB installation, you
will see that the "Select Migration Source" window (what you see
after starting Migration Workbench) now reflects MySQL and SQL Server. Select
SQL Server and note that the previous Oracle Model for the MySQL migration will
be truncated. And like before, Migration Workbench will start the Capture
We will finish Part Four
here. If you want to continue on your own, follow the instructions in the
wizard. Without modifying the SQL Server data source, you will encounter a
number of errors as shown below.
At this point in the
process, we are ready to create a new Oracle Model - well, almost. There is
some detailed reading in the User's Guide you have to perform because the "online"
SQL Server migration process requires manual adjustments or editing of some SQL
Server objects (views and stored procedures in the Northwind case). In Part Five,
we will perform the migration process and look at what has to be done to
prepare a SQL Server database for use with Oracle Migration Workbench.
See All Articles by Columnist Steve Callan