Message-Id: <10637.118338@fatcity.com> From: "Woody Mckay" Date: Mon, 2 Oct 2000 15:11:38 -0400 Subject: RE: Oracle Migration Workbench 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: 1. Gather the logical model from SQL Server. 2. Create the logical model in Oracle. 3. 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@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
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.
 
There=20 are three steps:
 
1.=20 Gather the logical model from SQL Server.
2.=20 Create the logical model in Oracle.
3.=20 Create the physical model in Oracle.
 
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.  Some of the mappings between SQL Server and = Oracle can=20 be changed from their defaults.
 
Sincerely,
 
Woody
-----Original Message-----
From: Sanjay Kumar=20 [mailto:ora_user@hotmail.com]
Sent: Monday, October 02, 2000 = 3:06=20 PM
To: Oracle List (Telelist); Oracle Discussion=20 List
Subject: Oracle Migration = Workbench

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