69 lines
4.4 KiB
HTML
69 lines
4.4 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="The performance architecture of the iSeries Access for Windows ODBC driver" />
|
|
<meta name="abstract" content="For the iSeries Access for Windows ODBC driver, all of the internal data flows between the client and the server are chained together, and transmit only when needed." />
|
|
<meta name="description" content="For the iSeries Access for Windows ODBC driver, all of the internal data flows between the client and the server are chained together, and transmit only when needed." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaikperftuneodbc.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="odbcselectcommitctl.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="odbcfinetunercdblock.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="useedsql.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="odbcperfarch" />
|
|
<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>The performance architecture of the iSeries Access for Windows ODBC
|
|
driver</title>
|
|
</head>
|
|
<body id="odbcperfarch"><a name="odbcperfarch"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">The performance architecture of the <span class="keyword">iSeries Access for Windows</span> ODBC
|
|
driver</h1>
|
|
<div><p>For the <span class="keyword">iSeries™ Access for Windows<sup>®</sup></span> ODBC
|
|
driver, all of the internal data flows between the client and the server are
|
|
chained together, and transmit only when needed.</p>
|
|
<div class="section"><p>This reduces server utilization because communications-layer resources
|
|
are allocated only once. Response times improve correspondingly.</p>
|
|
</div>
|
|
<div class="section"><p>These types of enhancements are transparent to the user. However,
|
|
there are some enhancements which are exposed on the iSeries Access for Windows ODBC
|
|
Setup dialog. Look at the online help on the <span class="uicontrol">Peformance</span> tab
|
|
of the setup GUI or refer to the Performance options on the Connection String
|
|
keywords descriptions for more information. A few of these performance options
|
|
are also discussed in more detail at the following links: </p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="odbcselectcommitctl.htm">Select a stringent level of commitment control</a></strong><br />
|
|
Do not use commitment control unnecessarily. The overhead that
|
|
is associated with locking not only increases utilization, but also reduces
|
|
concurrency. However, if your application is not read-only, commitment control <em>may</em> be
|
|
required.</li>
|
|
<li class="ulchildlink"><strong><a href="odbcfinetunercdblock.htm">Fine-tune record-blocking</a></strong><br />
|
|
<strong>Record-blocking</strong> is a technique that significantly reduces
|
|
the number of network flows. </li>
|
|
<li class="ulchildlink"><strong><a href="useedsql.htm">Use Extended Dynamic SQL</a></strong><br />
|
|
Use the ODBC call level interface to dynamically run your SQL statements.</li>
|
|
</ul>
|
|
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaikperftuneodbc.htm" title="A key consideration for ODBC application developers is achieving maximum performance from client/server applications.">Performance-tuning iSeries Access for Windows ODBC</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |