Browse Prior Art Database

FAST and Secure Stored Procedures for a Client/Server DBMS

IP.com Disclosure Number: IPCOM000114582D
Original Publication Date: 1995-Jan-01
Included in the Prior Art Database: 2005-Mar-29
Document File: 4 page(s) / 138K

Publishing Venue

IBM

Related People

Che, CW: AUTHOR [+2]

Abstract

A method for improving the database performance by using a private communication protocol in a client server environment is disclosed. The Stored Procedure provides a simple interface to minimize the network traffic by performing a batch of database activities on the database server locally.

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

FAST and Secure Stored Procedures for a Client/Server DBMS

      A method for improving the database performance by using a
private communication protocol in a client server environment is
disclosed.  The Stored Procedure provides a simple interface to
minimize the network traffic by performing a batch of database
activities on the database server locally.

      In this design, the network traffic problem is solved by using
a technique commonly known as 'Stored Procedure'.  Users can write a
procedure and store it at the database server.  Remote client
applications can invoke this Stored Procedure to be executed at the
database server machine by sending a special request to the server.
The Stored Procedure then carries out all datatabase requests locally
at the database server machine.  As a result, there are only 2
network messages - one for the initial request to invoke the Stored
Procedure and the other a reply from the database server back to the
client, when the Stored Procedure is complete.  This is shown below:
     CLIENT           NETWORK                  SERVER
     Stored   ------------------------> invokes
     Procedure                          Stored
     Request                            Procedure --> Stored
                                                      Procedure:
                                                 <--- Query #1
                                                 ---->
                                                 <--- Query #2
                                                 ---->
                                                   .
                                                   .
                                                 <--- Query #n
                                                 ---->
                                                      Stored
              <-------------------------------------- Procedure
                                                      Response

      In order to prevent database corruption, in this design, Stored
Procedure is executed in a different process and address space than
the
database server.  This makes the internal database server data
structures
and files on which data integrity rely, inaccessible to the
user-written
code executing in the Stored Procedure.  This is shown in the
following...