Re: Any experience converting MSSQL apps to Oracle?

Ilia Sazonov <ilia_sazonov_at_arktur.ru> wrote in message news:38e300b6_at_news.ptt.ru...
> I would add one more important thing:
> You may have stored procedures returning recordsets (like a common select)
> in MS SQL.
> Oracle does not provide this feature.

Well, that's not entirely true. Oracle supports result sets from stored procedures, it just does it significantly different than MSSQL. Output variables, like ref cursors, must be used to get stored proc result sets.

>
>
> Malcontent <malcontent_at_msgto.com> wrote in message
> news:38E2FECB.6EF1C639_at_msgto.com...
> > > Any gotchas you would like to share?

Not much else, other than learning to admin Oracle is kind of a bitch. Expect several days of reading docs and learning stuff just to get Enterprise Manager installed and working correctly. Migration Workbench is a decent tool to start the conversion, but it won't do everything for you.

My best advice is to use this forum (you can do usenet searches from www.deja.com and find past articles) to find answers.

Good Luck,
Josh Miller

> >
> > Here are two.
> >
> > In Oracle you are limited to object names of 30 characters or less. If
> > you have fields or tables with more then 30 characters you are going to
> > suffer.
> >
> > SQL server processes where clauses in a case insensitive manner. Oracle
> > does not. In SQL server the following two queries return the same
> > recordset.
> >
> > select * from a where field="something" == select * from a where
> > field="SomeThing"
> >
> > In oracle these will return different recordsets.
> >
> > I am sure there is a bunch or SQL differences too. Your code is probably
> > full of statements containing "LEFT OUTER JOIN" which does not work in
> > oracle.
> >
>
>
Received on Thu Mar 30 2000 - 00:00:00 CST