62 lines
4.5 KiB
HTML
62 lines
4.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="Memory-resident database monitor row identification" />
|
||
|
<meta name="abstract" content="The join key column QQKEY simplifies the joining of multiple tables together. This column replaces the join field (QQJFLD) and unique query counters (QQCNT) that the database monitor used. The join key column contains a unique identifier that allows all of the information for this query to be received from each of the tables." />
|
||
|
<meta name="description" content="The join key column QQKEY simplifies the joining of multiple tables together. This column replaces the join field (QQJFLD) and unique query counters (QQCNT) that the database monitor used. The join key column contains a unique identifier that allows all of the information for this query to be received from each of the tables." />
|
||
|
<meta name="DC.Relation" scheme="URI" content="mbdma.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="memresrowid" />
|
||
|
<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>Memory-resident database monitor row identification</title>
|
||
|
</head>
|
||
|
<body id="memresrowid"><a name="memresrowid"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1">Memory-resident database monitor row identification</h1>
|
||
|
<div><p>The join key column QQKEY simplifies the joining of multiple tables
|
||
|
together. This column replaces the join field (QQJFLD) and unique query counters
|
||
|
(QQCNT) that the database monitor used. The join key column contains a unique
|
||
|
identifier that allows all of the information for this query to be received
|
||
|
from each of the tables.</p>
|
||
|
<div class="section"><p>This join key column does not replace all of the detail columns
|
||
|
that are still required to identify the specific information about the individual
|
||
|
steps of a query. The Query Definition Template (QDT) Number or the Subselect
|
||
|
Number identifies information about each detailed step. Use these columns
|
||
|
to identify which rows belong to each step of the query process: </p>
|
||
|
<ul><li>QQQDTN - Query Definition Template Number</li>
|
||
|
<li>QQQDTL - Query Definition Template Subselect Number (Subquery)</li>
|
||
|
<li>QQMATN - Materialized Query Definition Template Number (View)</li>
|
||
|
<li>QQMATL - Materialized Query Definition Template Subselect Number (View
|
||
|
w/ Subquery)</li>
|
||
|
<li>QQMATULVL - Materialized Query Definition Template Union Number (View
|
||
|
w/Union)</li>
|
||
|
</ul>
|
||
|
<p>Use these columns when the monitored query contains a
|
||
|
subquery, union, or a view operation. All query types can generate multiple
|
||
|
QDT's to satisfy the original query request. The server uses these columns
|
||
|
to separate the information for each QDT while still allowing each QDT to
|
||
|
be identified as belonging to this original query (QQKEY).</p>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div>
|
||
|
<div class="familylinks">
|
||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="mbdma.htm" title="The Memory-Resident Database Monitor is a tool that provides another method for monitoring database performance. This tool is only intended for SQL performance monitoring and is useful for programmers and performance analysts. The monitor, with the help of a set of APIs, takes database monitoring information and manages them for the user in memory. This memory-based monitor reduces CPU overhead as well as resulting table sizes.">Monitoring your queries using memory-resident database monitor</a></div>
|
||
|
</div>
|
||
|
</div>
|
||
|
</body>
|
||
|
</html>
|