ibm-information-center/dist/eclipse/plugins/i5OS.ic.dbmult_5.4.0.1/cqeoptimize.htm

48 lines
3.1 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="concept" />
<meta name="DC.Title" content="CQE query optimization considerations" />
<meta name="abstract" content="The Classic Query Engine (CQE) optimizer optimizes the query using the first partition member in the partitioned table. This access method is used to access rows from all of the partitions." />
<meta name="description" content="The Classic Query Engine (CQE) optimizer optimizes the query using the first partition member in the partitioned table. This access method is used to access rows from all of the partitions." />
<meta name="DC.Relation" scheme="URI" content="cqe.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="cqeoptimize" />
<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>CQE query optimization considerations</title>
</head>
<body id="cqeoptimize"><a name="cqeoptimize"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">CQE query optimization considerations</h1>
<div><p>The Classic Query Engine (CQE) optimizer optimizes
the query using the first partition member in the partitioned table. This
access method is used to access rows from all of the partitions.</p>
<p>DB2<sup>®</sup> UDB
Symmetric Multiprocessing feature data access methods cannot be used to access
a partitioned table, but they can be used when processing temporary tables
and for creating temporary indexes.</p>
<p>If the partitioned table is used in a query containing a subquery, the
optimizer does not attempt to implement the query as a join composite query.
This keeps the partitioned table from being materialized because of the join.</p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="cqe.htm" title="When queries are implemented using Classic Query Engine (CQE), you need to be aware of how the query is optimized including materialization and index usage.">Queries using Classic Query Engine</a></div>
</div>
</div>
</body>
</html>