Re: Stored Procedure Examples

John Doe wrote:

> Thanks man, I think that'll do it for me. As an OraNewbie, Oracle is a a
> bit confusing when you are used to doing something another way(in most's
> opionin here the 'wrong way') wish me luck!
>
> "Daniel A. Morgan" <dmorgan_at_exesolutions.com> wrote in message
> news:3B09F165.2D0ACA62_at_exesolutions.com...
> > John Doe wrote:
> >
> > > I'm looking for a few good examples of stored procedures that return
> > > recordsets. I come from the MS world, and it looks as if Oracle handles
> > > recordsets very differently as return values from stored procedures. I
 am
> > > unable to locate any examples from Oracle, and a few from some
 publishers,
> > > but the examples are lacking and sort 'Hello Worldish' I am looking
> > > specifically for stored procedures that are accepting multiple values,
 but
> > > do not require all of them, for example;
> > >
> > > I have a table of personnel. I want to be able to pass an employee id,
> > > first name, and / or last name to one procedure that will find the
 personnel
> > > that match one, two or three of the parameters I've passed it. In MS
 SQL I
> > > would use the datalength() to see if the param is null and build a
 string
> > > variable to exec(). It doesn't look like I can do this in Oracle. Help?
 I
> > > am a total newbie with Oracle and need a little guidance.
> > >
> > > Thanks in advance.
> >
> > Look up REF CURSOR in a good PL/SQL book.
> >
> > And you are correct. Oracle handles just about everything differently from
 SQL
> > Server. Like platform compatibility, operating system compatibility,
 stability,
> > security, scalability, record locking, and performance.
> >
> > You can't get Oracle's advantages without Oracle.
> >
> > Daniel A. Morgan
> >

I wish you luck. And I will pass on a bit of advise.

There is a reason why people that know Oracle are paid more than those that know SQL Server.

And there is a reason why large companies migrate applications from SQL Server to Oracle and not the other way around. Sort of like the reason people used to defect from East Germany to West Germany but not the other way around.

My advise is to treat them like to entirely separate products. Just forget SQL Server and assume that most of what you know doesn't apply. For example you will never do an outer join in Oracle like you did in SQL Server.

Start fresh and with a clean slate and you will do well. Try to make Oracle work and behave like a Microsoft product and the better you are at it the more likely you will produce a piece of garbage if you produce anything at all.

Daniel A. Morgan Received on Wed May 23 2001 - 00:54:02 CDT