Browse Prior Art Database

Run Procedure SQL Statement for the OS/2 Database Manager

IP.com Disclosure Number: IPCOM000122623D
Original Publication Date: 1991-Dec-01
Included in the Prior Art Database: 2005-Apr-04
Document File: 6 page(s) / 213K

Publishing Venue

IBM

Related People

Boykin, JR: AUTHOR [+2]

Abstract

A method is described which will provide a facility to execute user- composed programs against a database at the location of that database. The invention is being proposed to the SQL Language Council as an SQL extension to the SAA* (System Application Architecture) Database CPI (Common Programming Interface). Background

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 30% of the total text.

Run Procedure SQL Statement for the OS/2 Database Manager

      A method is described which will provide a facility to
execute user- composed programs against a database at the location of
that database.  The invention is being proposed to the SQL Language
Council as an SQL extension to the SAA* (System Application
Architecture) Database CPI (Common Programming Interface).
Background

      In the database application environment there are many
situations which are repetitive: receiving a fixed set of inputs,
performing the same multiple requests of a database, and returning a
fixed set of outputs. Typically, this is accomplished using several
SQL  statements.  Each SQL statement, in the distributed environment,
would require at least two data transmissions  over a LAN.  If a
transaction is comprised of many SQL statements,  it is easy to see
that this would result in considerable network traffic. Furthermore,
if many nodes are simultaneously executing the same transaction, the
network activity would be multiplied. This concurrent activity would
result in a performance degradation for the entire LAN.  With future
trends  heading towards a heavy client[server environment,  it is not
difficult to see that the amount of LAN activity will directly affect
the performance of the overall Database Management System.

      The OS/2* Database  Manager currently provides a facility to
execute the function on the remote node.  This facility is known as
the Database Application Remote Interface (DARI).  DARI is
implemented in the form of an API.  This facility furnishes the means
to execute  a user-generated "stored function" remotely against a
specified database.  A stored function is a program which is created
by the user and is built into a Dynamic Link Library (DLL) or a REXX
command file.

      Applications using DARI can drastically reduce network traffic
by reducing both the quantity of data and the number of trips used to
send it across the network.  This results in improved application
throughput and user response time. Applications executing SQL
statements that can be grouped together in a server procedure will
also benefit.  With one function call, all of the SQL statements
(located at the server and contained in the server procedure) are
executed. Network traffic is limited to one send and one receive (one
"round trip").  If DARI was not used, the same application would
require at least one round trip for each SQL statement executed.
This yields a performance increase of the overall throughput of the
Database Management System resulting from the reduction in trip/LAN
overhead.

      The use of DARI can greatly enhance the performance of OS/2 EE
Database Manager (DBM).  Consider the National Software Testing Lab
(NSTL) example.  When NSTL did initial testing of the Database
Manager, they were not aware of DARI.  Consequently, it was not
utilized in their tests.  As a result the Database Manager was
...