Re: A PL/SQL parameter puzzle

KurtisK wrote:

> We performed a very successful port of SQLServer to Oracle. And not just
> simple SQL statements. We ported over 500 stored procs that do XML
> shredding of incoming XML requests into data that is then validated inside
> the procedures and then either used to update tables or just return data.
> Of course we had to do some things differently in Oracle. Some inline
> functions used in our SQL statements caused major performance drags in
> Oracle so we had to work around that issue. Oracle's XML technology is much
> different syntantically speaking, so that all changed. etc, etc.
>
> It was interetesting to find that Oracle performed slower in many scenarios
> whereas our preconception was that it would perform better than SQLServer.
> This of course all depends on what you are doing with the code which Oracle
> is much more flexible and scalable in many ways.
>
> Kurt
>

I am involved in a project where SQL Server is ported to Oracle, with some 4800 procedures. And it does not work. Migration Workbench is a PITA; though support was great - we even got the beta releases to work with.
We are (still) resolving coding problems, like temporary tables, date issues (as Craig mentions: Craig: a date is merely a number: just add and subtract them, and then display with the correct format!), locking and referential integrity.

After adapting the pl/sql code, Oracle outperforms SQL Server.

Bottom line: SS2K <> Oracle.
Take the idea, and reprogram in Oracle.

-- 

Regards,
Frank van Bortel