85 lines
4.7 KiB
HTML
85 lines
4.7 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="Performance considerations of common end-user tools" />
|
||
|
|
<meta name="abstract" content="Having an ODBC driver that is optimally tuned is only part of the performance equation. The other part is the tools that are used; whether they are used simply to query the data, or to build complex programs." />
|
||
|
|
<meta name="description" content="Having an ODBC driver that is optimally tuned is only part of the performance equation. The other part is the tools that are used; whether they are used simply to query the data, or to build complex programs." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaikodbcperfconsd.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiktoolsbadperf.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="odbcendusertools" />
|
||
|
|
<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>Performance considerations of common end-user tools</title>
|
||
|
|
</head>
|
||
|
|
<body id="odbcendusertools"><a name="odbcendusertools"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Performance considerations of common end-user tools</h1>
|
||
|
|
<div><p>Having an ODBC driver that is optimally tuned is only part of the
|
||
|
|
performance equation. The other part is the tools that are used; whether they
|
||
|
|
are used simply to query the data, or to build complex programs.</p>
|
||
|
|
<div class="section"><p>Some of the more common tools include: </p>
|
||
|
|
<ul><li>Crystal Services Crystal Reports Professional</li>
|
||
|
|
<li>Cognos Impromptu</li>
|
||
|
|
<li>Gupta <span class="keyword">SQL</span> Windows<sup>®</sup></li>
|
||
|
|
<li>IBM<sup>®</sup> Visualizer
|
||
|
|
for Windows</li>
|
||
|
|
<li>Lotus<sup>®</sup> Approach<sup>®</sup></li>
|
||
|
|
<li>Lotus
|
||
|
|
Notes<sup>®</sup></li>
|
||
|
|
<li>Notes<sup>®</sup> Pump</li>
|
||
|
|
<li>Microsoft<sup>®</sup> Access</li>
|
||
|
|
<li>Microsoft Internet
|
||
|
|
Information Server</li>
|
||
|
|
<li>Microsoft SQL
|
||
|
|
Server</li>
|
||
|
|
<li>Microsoft Visual
|
||
|
|
Basic</li>
|
||
|
|
<li>Powersoft PowerBuilder</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>There are many more tools available than are on this list, and
|
||
|
|
every tool in the marketplace has its own strengths, weaknesses, and performance
|
||
|
|
characteristics. But most have one thing in common: support for ODBC database
|
||
|
|
servers. However, because ODBC serves as a common denominator for various
|
||
|
|
database management systems, and because there are subtle differences from
|
||
|
|
one ODBC driver to the next, many tool providers write to the more common
|
||
|
|
ODBC and <span class="keyword">SQL</span> interfaces.
|
||
|
|
By doing this, they avoid taking advantage of a unique characteristic of a
|
||
|
|
particular database server. This may ease programming efforts, but it often
|
||
|
|
degrades overall performance.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"> <dl><dt class="dlterm">Examples of ODBC performance-degrading tools:</dt>
|
||
|
|
<dd><a href="rzaiktoolsbadperf.htm#toolsbadperf">Examples: Common tool behaviors that degrade ODBC performance</a></dd>
|
||
|
|
</dl>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaiktoolsbadperf.htm">Examples: Common tool behaviors that degrade ODBC performance</a></strong><br />
|
||
|
|
The following examples demonstrate performance problems that are
|
||
|
|
associated with writing <span class="keyword">SQL</span> and
|
||
|
|
ODBC calls that do NOT take advantage of a unique feature of a particular
|
||
|
|
ODBC driver or the server database management system.</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>
|