Re: Oracle vs. Sybase

Just the reverse, PL/SQL (not shouting, it's just the way it's normally written) code stored in the database or executed from an application are extremely fast and effective.

There are an extremely good thing is most cases. One feature I find a lot of people ignore is packages which can provide improved performance from multiple procedures and the ability to hide access to code via scoping.

>> Serious question: I'm an old sybase dba and have recently been handed an
> Oracle project. I was planning on using a lot of pl/sql, but I'm
 wondering
> what the down side is. The above seems to imply that pl/sql is a thing
 to
> be avoided. Maybe it's my Sybase background but I figured stored procs
 to
> be a GOOD thing. At the very least it localizes the business rules and
> cuts out some of the compiling the server has to do. Isn't that true in
> Oracle?
>
Received on Wed Jun 25 1997 - 00:00:00 CDT