Oracle Migration Workbench - Part Three - Page 2
November 22, 2004
The Oracle Model versus the Oracle database
What is the difference between the Oracle Model and the Oracle database? In a way, you can view the Oracle Model as Oracle's interpretation of what the source database looks like. This interpretation is stored in the repository, and the migration takes that picture and creates the actual Oracle database objects.
The source model is represented in the Source Model pane.
You can then compare it to the Oracle Model, shown by selecting the other tab at the bottom of the console.
This visual representation of the schema (the objects, not the actual data) is useful in helping you understand how the source was translated into Oracle. We will see this again with SQL Server.
Getting Started with SQL Server
As mentioned when we entered the MySQL phase, there will be some administrative overhead involved in getting your SQL Server migration environment set up and configured. If this is the first time you have laid hands on SQL Server, you will be amazed at how similar Microsoft's flagship database product is to Oracle. If you are familiar with Oracle's Standard Edition One (appears in the 10g family), you will immediately see how SE1 is geared to compete with SQL Server in the small-to-medium business market. You can read more about SE1 at http://www.oracle.com/database/product_editions.html.
Where to get SQL Server
Microsoft has a similar setup compared to Oracle. Oracle's OTN is Microsoft's MSDN, but one main difference has to do with downloading Microsoft products. You can get SQL Server off of Microsoft's main site as opposed to the MSDN site (or domain). The link for SQL Server 2000 is http://www.microsoft.com/downloads/details.aspx?FamilyID=d20ba6e1-f44c-4781-a6bb-f60e02dc1335&DisplayLang=en. If you want a CD, you can order that from Microsoft (see the instructions at the bottom of the page). Note that this is only a 120-day license (as opposed to no time limit on Oracle products). Installation is simple, but if you want a step-by-step guide to read before hand, you'll need to invest in a book or two.
SAMS' Teach Yourself Microsoft SQL Server 2000 in 21 Days (Second Edition) takes you through the installation process (and includes numerous screen shots). What I really like about the installation coverage in the book (Day 2) is the section on "Postinstallation: What Did You Get?" If you are familiar with Access, then you will recognize the Northwind database. Because of its popularity in Access, Microsoft includes Northwind with SQL Server. In the SQL Server to Oracle migration process using Migration Workbench, the Northwind database will be the source I will use.
The two critical tasks to get set up for SQL Server are to install it and create a user account on the Northwind database. If you use the SAMS book as a guide, look at Chapter 10 and create a user who has Northwind as his default database (plus grant a healthy dose of privileges for now). If you do not have the book, you can use the online books (Start>Programs>Microsoft SQL Server>Books Online).
Look for Logging In to SQL Server. If you think "Enterprise Manager" and follow what seems logical (keeping in mind how OEM works in Oracle), navigate to the Northwind database users and create a user (you).
Using the Enterprise Manager, add yourself as a user of the Northwind database.
These screenshots show how I created my account using my Windows login account.
You can also use Action>New Database User via the console menu options, and if you want the step-by-step approach, use the Create Login Wizard (via Tools>Wizards).
Once you have a usable account, login via the SQL Query Analyzer, drill down to the Northwind database and try your hand at running a query.
This part of the series covered more features of Migration Workbench and helped to get you started on becoming familiar with SQL Server. In the next part, I will go into more detail about SQL Server (how to translate "SQL Server" into "Oracle") and start the migration process for migrating the Northwind database to an Oracle database. Additionally, we will take a quick look at SQL Server's ability to connect to other databases.