74 lines
4.8 KiB
HTML
74 lines
4.8 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="reference" />
|
||
|
|
<meta name="DC.Title" content="Stored procedures" />
|
||
|
|
<meta name="abstract" content="Stored procedures commonly are used in client/server applications, especially in the area of online transaction processing (OLTP), since they can provide performance, transaction-integrity and security benefits." />
|
||
|
|
<meta name="description" content="Stored procedures commonly are used in client/server applications, especially in the area of online transaction processing (OLTP), since they can provide performance, transaction-integrity and security benefits." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaikodbcperfconsd.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaikspresultsets.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaikspex.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1999, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1999, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="odbcstoredproc" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>Stored procedures</title>
|
||
|
|
</head>
|
||
|
|
<body id="odbcstoredproc"><a name="odbcstoredproc"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Stored procedures</h1>
|
||
|
|
<div><p>Stored procedures commonly are used in client/server applications,
|
||
|
|
especially in the area of online transaction processing (OLTP), since they
|
||
|
|
can provide performance, transaction-integrity and security benefits.</p>
|
||
|
|
<div class="section"><p>For information regarding specific SQL commands that are used
|
||
|
|
in the examples of stored procedures, see the <em>SQL Reference</em> book. View
|
||
|
|
an HTML online version of the book, or print a PDF version, from the <a href="../db2/rbafzmst02.htm">DB2
|
||
|
|
Universal Database™ for iSeries™ SQL Reference</a> iSeries Information Center topic.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>The illustration below shows an application where one transaction
|
||
|
|
consists of four separate I/O operations, each that requires an SQL statement
|
||
|
|
to be processed. In the client/server environment, this requires a minimum
|
||
|
|
of eight messages between the server and the client, as shown. This can represent
|
||
|
|
significant overhead, especially where the communication speed is slow (for
|
||
|
|
example over a dial-up line), or where the turnaround speed for the connection
|
||
|
|
is slow (for example over a satellite link).</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p><br /><img src="rv3w347.gif" alt="Client/server application without stored procedure" /><br /></p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>The following illustration shows the same transaction by a stored
|
||
|
|
procedure on the server. As illustrated, the communications traffic has been
|
||
|
|
reduced to a single message pair. There are additional benefits. For example,
|
||
|
|
the procedure can arrange to send back only the data that is absolutely required
|
||
|
|
(for example, just a few characters from a long column). A DB2<sup>®</sup> for <span class="keyword">i5/OS™</span> stored procedure can be any iSeries program,
|
||
|
|
and does not have to use SQL for data access.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p><br /><img src="rv3w348.gif" alt="Client/server application with stored procedure" /><br /></p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaikspresultsets.htm">Stored procedure result sets</a></strong><br />
|
||
|
|
Define scrollable SQL stored procedure result sets.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaikspex.htm">Examples: Stored procedures</a></strong><br />
|
||
|
|
View examples of stored procedures.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaikodbcperfconsd.htm" title="See any of the following ODBC performance topics.">iSeries Access for Windows ODBC performance</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|