Re: A PL/SQL parameter puzzle

Maybe in some cases. In ours, OMWB could not handle the conversion. Our T-SQL procedures stream XML directly from SQL statements which is the most efficient way in the Microsoft environment. In Oracle you can't do this, so we needed to append xml results to an in/out parameter. Also, T-SQL error handling stinks. Oracle's exception managment facilities are superior. The OMWB couldn't properly map the logic in the procs to Oracle.

When it comes to ordinary procedures that mostly use CRUD statements, I imagine OMWB could do a good job.

Kurt

-- 


----------------------------------------------------
This mailbox protected from junk email by MailFrontier Desktop
from MailFrontier, Inc. http://info.mailfrontier.com

"Frank van Bortel" <fvanbortel_at_netscape.net> wrote in message
news:cndgjl$231$1_at_news4.zwoll1.ov.home.nl...


> KurtisK wrote:

> > We didn't use Migration Workbench.  You are right in that the OMWB can't

> > convert stored procs.  It can help in transferring data and table

> > structures.  All the code did needed rewritten in Oracle PL/SQL, DML and

> > DDL.  We had to resolve all the issues you mentioned with temp tables,

> > dates, implementing RI, etc.

> >

>

> Craig did.

> OMWB *can* convert stored procedures - it just is TSQL,

> converted to PL/SQL...

> -- 

>

> Regards,

> Frank van Bortel