56 lines
4.5 KiB
HTML
56 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="concept" />
|
||
|
|
<meta name="DC.Title" content="SQE and CQE Engines" />
|
||
|
|
<meta name="abstract" content="To fully understand the implementation of query management and processing in DB2 UDB for iSeries on i5/OS V5R2 and subsequent releases, it is important to see how the queries were implemented in releases of i5/OS previous to V5R2." />
|
||
|
|
<meta name="description" content="To fully understand the implementation of query management and processing in DB2 UDB for iSeries on i5/OS V5R2 and subsequent releases, it is important to see how the queries were implemented in releases of i5/OS previous to V5R2." />
|
||
|
|
<meta name="DC.subject" content="SQE engine, CQE engine, definitions, SQE, CQE" />
|
||
|
|
<meta name="keywords" content="SQE engine, CQE engine, definitions, SQE, CQE" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="queryoptimize.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="rzajqsqecqe" />
|
||
|
|
<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>SQE and CQE Engines</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzajqsqecqe"><a name="rzajqsqecqe"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">SQE and CQE Engines</h1>
|
||
|
|
<div><p>To fully understand the implementation of query management and
|
||
|
|
processing in DB2<sup>®</sup> UDB
|
||
|
|
for iSeries™ on <span class="keyword">i5/OS™</span> V5R2 and subsequent releases,
|
||
|
|
it is important to see how the queries were implemented in releases of <span class="keyword">i5/OS</span> previous to V5R2.</p>
|
||
|
|
<p>The figure below shows a high-level overview of the architecture of DB2 UDB
|
||
|
|
for iSeries before <span class="keyword">i5/OS</span> V5R2. The optimizer and database
|
||
|
|
engine are implemented at different layers of the operating system. The interaction
|
||
|
|
between the optimizer and the database engine occurs across the Machine Interface
|
||
|
|
(MI). <br /><img src="rzajq552.gif" alt="Description of pre-V5R2 optimizer. The query runs through the network to the host server to the optimizer. The optimizer is above the SLIC level." /><br /></p>
|
||
|
|
<p>The figure below shows an overview of the DB2 UDB for iSeries architecture on <span class="keyword">i5/OS</span> V5R3
|
||
|
|
and where each SQE component fits. The functional separation of each SQE component
|
||
|
|
is clearly evident. In line with design objectives, this division of responsibility
|
||
|
|
enables IBM<sup>®</sup> to
|
||
|
|
more easily deliver functional enhancements to the individual components of
|
||
|
|
SQE, as and when required. Notice that most of the SQE Optimizer components
|
||
|
|
are implemented below the MI. This translates into enhanced performance efficiency.<br /><img src="rzajq551.gif" alt="Description of optimizer after V5R2. The query runs from the interface through the network to the host server. From there it goes to the optimizer and the query dispatcher. The query dispatcher determines whether the query will run through CQE or SQE. The CQE database engine exists in SLIC. The SQE optimizer also exists in SLIC, as does the SQE statistics manager and the SQE data access primitives." /><br /></p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="queryoptimize.htm" title="DB2 UDB for iSeries provides two query engines to process queries: the Classic Query Engine (CQE) and the SQL Query Engine (SQE).">Query Engine Overview</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|