Re: PLSQL for MS Sql server devs?

An database conists of one or more instances, thus I would say:

database.instance.schema.object.

Anjo.

Nuno Souto wrote:

> On Sat, 12 May 2001 18:19:41 GMT, duanez_at_hostrack.net (duanez) wrote:
>
> >that that is a database, which is a subset of the Instance? In MS SQL
> >server we had the heirarchy go SERVER.DATABASE.OBJECT. In Oracle is it
> >
> >INSTANCE.SCHEMA.OBJECT?
>
> Pretty much so. But take note of what Howard said. An instance is
> not exactly the same as a "database". And there can be many schemas
> in a database, executed by an instance (or two or three instances, in
> case of Parallel Server).
>
> Maybe a more accurate wording would be:
>
> INSTANCE.DATABASE.SCHEMA.OBJECT
>
> >
> >other questions i have are more directly related to programming
> >practices in PL SQL. In MS SQL server, we relied heavily on #temp
> >tables whereas in PL SQL i noticed (from other people's code) there is
> >great emphasis on cursors. How do you deal with no temp tables? Can a
> >PL SQL function return a 'table' or a recordset datatype as a result?
> >And then that rs be like table object and included in joins to other
> >objects?
>
> In PL/SQL there is a lond standing "thing" against temporary tables
> a-la Sybase. You can nest entire SELECT statements in the FROM clause
> to give you similar functionality. In 8i there are true temporary
> tables, similar to Sybase.
>
> >
> >If anyone has writen an FAQ or a Book with a title like "PL SQL for
> >ex-MS SQL Server Developers" that'd be great. If not, i'd like help
> >starting one.
>
> There is already a book that compares SS, Sybase, ORACLE and a few
> others. I've seen it somewhere. Have a look around the ORACLE
> website, there is quite a lot on Sybase and SS ==> ORACLE.
>
> Cheers
> Nuno Souto
> nsouto_at_bigpond.net.au.nospam
> http://www.users.bigpond.net.au/the_Den/index.html
  Received on Sun May 13 2001 - 12:12:30 CDT