Re: Sybase to Oracle migration

I am responsable for TSQL to PLSQL stored procedure conversion, please post specific bugs, fixes and or workarounds to infomwb_at_ie.oracle.com or post to the discussion forum on technet. It is hard for the Workbench team to get feedback from consultants and customers in the field beyond bugs being logged with no idea of priority, difficulty to fix, or difficulty to work around.

We would also like to have some sort of tool to gauge the time required for a migration (depending on number and complexity of stored procedures and or advanced facilities not automatically converted to oracle, for example windows specific sqlserver extentions) if you could post some rough guidelines for the time required, it would be useful.

Check out:

Oracle Migration Workbench on
http://technet.oracle.com/tech/migration/workbench/  may require free registration.

It has documentation and faq details. There is also a discussion board and a email help desk. Converts Sybase, (Microsoft) SQLServer, Access and (soon SQLAnywhere and mysql) to Oracle, includes stored procedure conversion.

Turloch

http://www.geocities.com/totierne/
latest version: 1.2.5.0.0 , 1.3.0.0.0 due soon

In article <%is85.6191$cu1.14896_at_news1.rdc1.ct.home.com>,   "LF" <frolio_at_home.com> wrote:
> Greetings Jaco, I recently went through a similar exercise. We were
 running
> Microsoft's
> SQL Server 7.0 and we wanted to migrate to Oracle 8.1.6. We talked
 with
> Oracle
> consulting and it appears that the Migration workbench will not
 transfer
> your procs 100%,
> you will still have to go in and tweak things here and there. Oracle
> consulting ended up
> costing too much money so decided to do the migration myself, I ended
 up
> rewriting all the
> procs to Oracle procs and packages manually. I used a few of our web
> programmers
> and the whole process took only two weeks or so. With regards to temp
> tables, Oracle
> has an object called "Global Temporary Table" which will work the same
 way
> as a temp
> table in SQL, the only difference is that the table is permanent and
 will
> not go away when
> the transaction is complete. I have been using such a table with
 success.
>
> L
>
> "jhgrobler" <jacog_at_pillar.co.za> wrote in message
> news:3961effe$0$231_at_hades.is.co.za...
> > Hi
> >
> > We are in the process of migrating our app from Sybase Adaptive
 Server to
> > Oracle.
> >
> > We are using the migration workbench. I am looking for information
 on the
> > pitfalls when migrating as well as what the suggested work arounds
 are
 for
> > the different errrors that the migration workbench produce (for
 instance
> > what the Oracle alternative are for using temporary or hash(#)
 tables in
> > stored procedures)
> >
> > We are mainly concerned with stored procedures since our whole app
 are
> > contained in stored procs in Sybase
> >
> > Thanks in advance
> >
> > Jaco Grobler
> > South Africa
> >
> >
>
>

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Wed Jul 12 2000 - 00:00:00 CDT