HP3000-L Archives

October 1995, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Rudderow, Evan" <[log in to unmask]>
Reply To:
Rudderow, Evan
Date:
Wed, 4 Oct 1995 12:53:00 EDT
Content-Type:
text/plain
Parts/Attachments:
text/plain (31 lines)
Eric Schubert <[log in to unmask]> wrote:
 
<snip>
 
>This sounds like a broad question but I need techno talk description of how
SQL
>engines work over a network.  I know the SQL spec is old and was written
when
>networks were not in force as in today's client/server world - so I was
wondering if
>there exists a spec for writing a "generic" SQL network server that any
"out of the
>box" SQL clients can communicate with.
>
>SQL is a standard query language in the fact that you can compile an SQL
host
>application on various platforms in the traditional view to work with a
host SQL
>DBMS - but what about the network protocol used between an SQL server and a
>client located on a network?  Does there exist a "spec" that supports
multi-vendor
>client access?  What is it?
 
I recently read Kyle Geiger's book "Inside ODBC".  He devotes a chapter or
so to networking issues and in fact describes the SQL/Server implementation.
 I get the impression that each vendor's network implementation is unique;
 that conclusion is supported by the fact that there are so many gateways
available to go from one RDBMS to another.
 
 -- Evan

ATOM RSS1 RSS2