[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference ulysse::rdb_vms_competition

Title:DEC Rdb against the World
Moderator:HERON::GODFRIND
Created:Fri Jun 12 1987
Last Modified:Thu Feb 23 1995
Last Successful Update:Fri Jun 06 1997
Number of topics:1348
Total number of notes:5438

794.0. "ORACLE- SQL*STAR, SQL*NET, SQL*CONNECT" by THEWAV::FRIEDMAN (Robin Friedman) Wed Nov 14 1990 00:43

I just finished reading some Oracle literature which mentioned
SQL*STAR, SQL*NET, and SQL*CONNECT. The literature just mentions
them without going into any details. 

Can you please help me position these?

Is SQL*STAR a product or an architecture?

It sounds like SQL*NET is used to communicate among different Oracle Databases.
Does this apply to:
  -DBs on the same VAX 
  -DBs on different VAXs
  -a DB on a VAX and a DB on a NON-VAX server


SQL*CONNECT sounds like a product to connect Oracle DBs with non ORACLE DBs
(i.e. DB2, RMS, etc...)



Thanks for you help,
Robin
T.RTitleUserPersonal
Name		DateLines
794.1From the mouth of Oracle Corp...HGOVC::DEANGELISMomuntaiWed Nov 14 1990 04:0126
From Oracle's SQL*DBA V6 manual...

"An ORACLE database can be used in a software configuration known as SQL*Star.
SQL*Star is a collection of software, installed to support distributed
processing or a distributed database, which usually includes the following
three ORACLE components:

ORACLE RDBMS:	The ORACLE RDBMS inherently contains the functionality to
		support distributed databases (for example, to support
		distributed queries), location transparency, and site autonomy.
		...

SQL*Connect:	This product is a "gateway" product to non-ORACLE databases, in
		particular SQL/DS and DB2. SQL*Connect permits some Oracle
		Corporation tools to operate on the non-ORACLE databases as if
		they were ORACLE databases. In conjunction with SQL*Net,
		SQL*Connect can be used on remote databases.

SQL*Net:	SQL*Net is the heterogeneous network interface component of
		SQL*star. It allows data to be sent across communications
		protocols and handles the transfer of data between various
		databases."

If you need more detail, let me know.

John.
794.2is SQL*NET transparent to the application?THEWAV::FRIEDMANRobin FriedmanWed Nov 14 1990 22:089
    Thanks for the info...
    
    Does an application specifically reference SQL*NET or is the location
    of the DB transparent to the application?
    
    For example: 
      I have an application running on a VAX accessing a DB
      on the same VAX. If I decide to move the DB to an ULTRIX DB server
      do I need to modify the application to reference the DB via SQL*NET?
794.3More on SQL*NetHGOVC::DEANGELISMomuntaiThu Nov 15 1990 04:4254
�             <<< Note 794.2 by THEWAV::FRIEDMAN "Robin Friedman" >>>
�                -< is SQL*NET transparent to the application? >-

�    Does an application specifically reference SQL*NET or is the location
�    of the DB transparent to the application?

Well, you need to tell Oracle at LOGON time where the database is located.
This depends on the interface of use, eg. With SQL*Forms, you typically start
it like this:

	RUNFORM formname [username/password] [@driver-prefix:nodename]

If you leave off the driver/node part the database is assumed to be local. If
you include it, a connection is made to the remote database. However, once in
the form the database location is transparent to the application.

From programs, again you have to connect to the database you're going to use.
This is done in the code via an

	EXEC SQL CONNECT usr IDENTIFIED BY passwd;

Here "usr" can refer to a username only, therefore the database is local, or
can include the driver/node spec identifying the database as remote. Once 
connected, all other SQL statements remain unchanged.

You can use multiple databases via a different syntax, eg.

	EXEC SQL BEGIN DECLARE...
		char host1[20] = " d:london";
		char host2[20] = " d:hkong";
	EXEC SQL END DECLARE...

	EXEC SQL DECLARE DB1 DATABASE;
	EXEC SQL DECLARE DB2 DATABASE;
	EXEC SQL CONNECT :usr IDENTIFIED BY :password
		AT DB1 USING :host1
		AT DB2 USING :host2;

	EXEC SQL AT DB1 DECALRE cursor_name CURSOR FOR SELECT...;
	EXEC SQL OPEN cursor_name...;

�    For example: 
�      I have an application running on a VAX accessing a DB
�      on the same VAX. If I decide to move the DB to an ULTRIX DB server
�      do I need to modify the application to reference the DB via SQL*NET?

As you can see above you may or may not have to do this depending on your
interface and how you specify the connect.

The other issue here is whether SQL*Net supports VAX to Ultrix connections.
My current docs don't explicitly say whether this is supported. It does support
Decnet and TCP/IP protocols, but I don't know what other support is required.

John.
794.4SQL*Net is supposedly transparentBROKE::THOMASFri Dec 14 1990 22:5310
    I'm no expert on SQL*Net, but my understanding is that it provides
    a transparent layer over DECnet, TCP/IP, X.25, and SNA.  You need 
    to install the appropriate SQL*Net environment(s) on every system 
    connected, but after that, applications/databases can communicate 
    without needing to know the underlying communications protocol.
    
    More on SQL*Connect -- SQL*Connect provides access to non-ORACLE
    databases (DB2, SQL/DS, and RMS) from selected ORACLE tools, namely
    SQL*Plus.  Please note that SQL*Connect is not available from
    SQL*Forms.