🚀 go-pugleaf

In article <1BZPBYYH@cc.swarthmore.edu> stauffer@cc.swarthmore.edu (Glenn Stauffer) writes:
>In article <9209021919.AA28877@coos.dartmouth.edu> Hades,
>hades@coos.dartmouth.edu writes:
>>using DAL as your means of communication. This requires the purchace of
>>the DAL Server for whatever machine is running the Oracle database
>
>For more versatility, you may want to investigate SQL*Net from Oracle.  I
>was at an Apple/Oracle
>presentation a few weeks ago and SQL*Net was touted over DAL. 
>Apparently, Oracle isn't
>too pleased with the DAL solution.  I'll dig out my notes and post later
>about things I
>learned at the presentation - including mention of a Quadra-based Oracle
>server.
>
>Glenn Stauffer
>Swarthmore College

I wouldn't expect Oracle to hype DAL over one of its own products, would you?!? The
downside of using SQL*Net is that all your front-end applications are hardwired into
Oracle, which is of course exactly what Oracle wants.  Having used DAL extensively on
several projects, I would be the first to say that it isn't a dream.  However you
are almost wholly independent of the back-end, be it Oracle, Sybase, Ingres, etc.

If you go into building your front-end applications with something like DAL, you gain
the ability to scale these applications well: start them off with a server on an A/UX
box, move it to a VAX, and on and on.

On the other hand, if you are an Oracle shop and have support contracts, etc, and are
not planning a migration or diversification soon, probably SQL*Net is the way to go
simply from the point of simplicity of support.

-John Jamison
 Swarthmore College class of '88
 Disclaimer:  these opinions are mine all mine!
-- 
-----------------
John Jamison
Bell Atlantic Healthcare Systems
jjamison@bellahs.com