RE: Oracle Migration Workbench

From: Woody Mckay <wmckay_at_hydrogenmedia.com>
Date: Mon, 2 Oct 2000 15:11:38 -0400
Message-Id: <10637.118338@fatcity.com>

This is a multi-part message in MIME format.

------=_NextPart_000_0020_01C02C83.1099B2A0 Content-Type: text/plain;

charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

I've used it several times. It migrates all the SQL Server objects to Oracle. I found there to be two basic types of objects -- objects with code (T-SQL) and objects without code. Objects without code migrate with no problem. Objects with code are problematic. The time to migrate depends on the number of stored procedures/triggers, complexity and length of code, and use of T-SQL specific syntax not available in PL/SQL.

There are three steps:

Gather the logical model from SQL Server.
Create the logical model in Oracle.
Create the physical model in Oracle.

Each step creates an execution log with specific details. These steps don't have to be executed in the same session because it is repository based. Some of the mappings between SQL Server and Oracle can be changed from their defaults.

Sincerely,

Woody
-----Original Message-----
From: Sanjay Kumar [mailto:ora_user_at_hotmail.com] Sent: Monday, October 02, 2000 3:06 PM To: Oracle List (Telelist); Oracle Discussion List Subject: Oracle Migration Workbench

Hi,

has anyone used Oracle Migration Workbench to migrate from SQL Server to Oracle?
If so, what are the factors that need to be kept in mind?

Rgds,
Sanjay Kumar

------=_NextPart_000_0020_01C02C83.1099B2A0 Content-Type: text/html;

charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">

<META content=3D"MSHTML 5.00.3018.900" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D029290519-02102000>I've=20
used it several times.  It migrates all the SQL Server objects to=20 Oracle.  I found there to be two basic types of objects -- objects = with=20
code (T-SQL) and objects without code.  Objects without code = migrate with=20
no problem.  Objects with code are problematic.  The time to = migrate=20
depends on the number of stored procedures/triggers, complexity and = length of=20
code, and use of T-SQL specific syntax not available in=20 PL/SQL.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D029290519-02102000></SPAN></FONT> </DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D029290519-02102000>There=20
are three steps:</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D029290519-02102000></SPAN></FONT> </DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D029290519-02102000>1.=20
Gather the logical model from SQL Server.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D029290519-02102000>2.=20
Create the logical model in Oracle.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D029290519-02102000>3.=20
Create the physical model in Oracle.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D029290519-02102000></SPAN></FONT> </DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D029290519-02102000>Each=20
step creates an execution log with specific details.  These steps = don't=20
have to be executed in the same session because it is repository=20 based.  </SPAN></FONT><FONT color=3D#0000ff face=3DArial = size=3D2><SPAN=20
class=3D029290519-02102000>Some of the mappings between SQL Server and = Oracle can=20
be changed from their defaults.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D029290519-02102000></SPAN></FONT> </DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D029290519-02102000>Sincerely,</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D029290519-02102000></SPAN></FONT> </DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D029290519-02102000>Woody</SPAN></FONT></DIV>
<BLOCKQUOTE style=3D"MARGIN-RIGHT: 0px">
  <DIV align=3Dleft class=3DOutlookMessageHeader dir=3Dltr><FONT = face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Sanjay Kumar=20   [mailto:ora_user_at_hotmail.com]<BR><B>Sent:</B> Monday, October 02, 2000 = 3:06=20
  PM<BR><B>To:</B> Oracle List (Telelist); Oracle Discussion=20   List<BR><B>Subject:</B> Oracle Migration = Workbench<BR><BR></DIV></FONT>

  <DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>has anyone used Oracle Migration =

Workbench to=20
migrate from SQL Server to Oracle?</FONT></DIV> <DIV><FONT face=3DArial size=3D2>If so, what are the factors that need = to be kept=20
in mind?</FONT></DIV>

  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Rgds,</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>Sanjay=20

Received on Mon Oct 02 2000 - 14:11:38 CDT