58 lines
3.5 KiB
HTML
58 lines
3.5 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="Optimizing grouping by adding additional grouping columns" />
|
||
|
<meta name="abstract" content="The same logic that is applied to removing grouping columns can also be used to add additional grouping columns to the query. This is only done when you are trying to determine if an index can be used to implement the grouping." />
|
||
|
<meta name="description" content="The same logic that is applied to removing grouping columns can also be used to add additional grouping columns to the query. This is only done when you are trying to determine if an index can be used to implement the grouping." />
|
||
|
<meta name="DC.Relation" scheme="URI" content="groupopt.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="rzajqgroupaddcols" />
|
||
|
<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>Optimizing grouping by adding additional grouping columns</title>
|
||
|
</head>
|
||
|
<body id="rzajqgroupaddcols"><a name="rzajqgroupaddcols"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1">Optimizing grouping by adding additional grouping columns</h1>
|
||
|
<div><p>The same logic that is applied to removing grouping columns can
|
||
|
also be used to add additional grouping columns to the query. This is only
|
||
|
done when you are trying to determine if an index can be used to implement
|
||
|
the grouping.</p>
|
||
|
<div class="section"><p>The following example illustrates a query where the optimizer
|
||
|
might add an additional grouping column. </p>
|
||
|
<pre> <strong>CREATE INDEX</strong> X1 <strong>ON</strong> EMPLOYEE
|
||
|
(LASTNAME, EMPNO, WORKDEPT)
|
||
|
|
||
|
<strong>DECLARE</strong> DEPTEMP <strong>CURSOR FOR
|
||
|
SELECT</strong> LASTNAME, WORKDEPT
|
||
|
<strong>FROM</strong> CORPDATA.EMPLOYEE
|
||
|
<strong>WHERE</strong> EMPNO = '000190'
|
||
|
<strong>GROUP BY</strong> LASTNAME, WORKDEPT
|
||
|
|
||
|
</pre>
|
||
|
</div>
|
||
|
<div class="section"><p>For this query request, the optimizer can add EMPNO as an additional
|
||
|
grouping column when considering <samp class="codeph">X1</samp> for the query.</p>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div>
|
||
|
<div class="familylinks">
|
||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="groupopt.htm" title="DB2 Universal Database for iSeries has certain techniques to use when the optimizer encounters grouping. The query optimizer chooses its methods for optimizing your query.">Grouping optimization</a></div>
|
||
|
</div>
|
||
|
</div>
|
||
|
</body>
|
||
|
</html>
|