Browse Prior Art Database

Generalized Blocking Procedures for Client-Server Environments

IP.com Disclosure Number: IPCOM000108474D
Original Publication Date: 1992-Jun-01
Included in the Prior Art Database: 2005-Mar-22
Document File: 4 page(s) / 136K

Publishing Venue

IBM

Related People

Amundsen, L: AUTHOR [+2]

Abstract

To improve performance in some database client-server environments, stored procedures can be used. Significant performance gains can be achieved when using stored procedures to perform custom record blocking. Custom record blocking allows large amounts of data to be passed across a network in blocks, instead of one record at a time. This reduces network overhead.

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

Generalized Blocking Procedures for Client-Server Environments

       To improve performance in some database client-server
environments, stored procedures can be used.  Significant performance
gains can be achieved when using stored procedures to perform custom
record blocking.  Custom record blocking allows large amounts of data
to be passed across a network in blocks, instead of one record at a
time.  This reduces network overhead.

      Performance gains from using this technique are offset by
additional coding effort, however.  Generally, one unique blocking
procedure is tailored to match one particular client procedure.  The
two procedures are designed to communicate specifically with each
other across the network in order to meet the needs of a particular
application.

      This article describes a technique of programming a generalized
blocking procedure using Database Manager.  A generalized blocking
procedure is a generic stored procedure designed to process blocks of
data for many client procedures.  Instead of being tailored to one
particular client procedure, a generalized blocking procedure can be
constructed to process arbitrary client requests using descriptive
information passed by the client procedure. This technique can reduce
the number of stored procedures required for applications, and thus
reduce the overhead of creating and maintaining the additional source
code.
BLOCKING PROCEDURE OVERVIEW

      An application using stored procedures is split into two parts:
a client procedure running on a client workstation, and a stored
procedure running on a database server.  When stored procedures are
used for custom record blocking, the two procedures are designed to
pass blocks of data across the network.

      In order to process records in blocks, the record structure and
the number of records to be passed must be specified.  This
information is usually defined as part of the procedures.  Several
applications making use of blocking procedures often have unique
client and stored procedures for each record type being blocked.

      This process is shown in Fig. 1.
GENERALIZED BLOCKING PROCEDURE

      To reduce total lines of code for applications, the concept of
a generalized blocking procedure can be used.  A generalized blocking
procedure is a stored procedure that is written to be independent of
the structure of the data being blocked.  It makes no assumptions
about the record structure or number of records being passed.
Instead, the information needed for blocking is supplied by the
client procedure at runtime.

      For example, if applications A and B perform queries, but on
different tables in a database, a generalized blocking procedure
could be wri...