56 lines
3.5 KiB
HTML
56 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="concept" />
|
|||
|
<meta name="DC.Title" content="Design files to reduce access path rebuilding time" />
|
|||
|
<meta name="abstract" content="File design can help reduce access path recovery time." />
|
|||
|
<meta name="description" content="File design can help reduce access path recovery time." />
|
|||
|
<meta name="DC.Relation" scheme="URI" content="rbaforzahfpro.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="rbaforzahfprq" />
|
|||
|
<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>Design files to reduce access path rebuilding time</title>
|
|||
|
</head>
|
|||
|
<body id="rbaforzahfprq"><a name="rbaforzahfprq"><!-- --></a>
|
|||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|||
|
<h1 class="topictitle1">Design files to reduce access path rebuilding time</h1>
|
|||
|
<div><p>File design can help reduce access path recovery time.</p>
|
|||
|
<p>For example, you might divide a large master file into a
|
|||
|
history file and a transaction file. The system uses the transaction file
|
|||
|
for adding new data. The system uses the history file for inquiry only. On
|
|||
|
a daily basis, you might merge the transaction data into the history file,
|
|||
|
then clear the transaction file for the next day's data. With this design,
|
|||
|
you shorten the time to rebuild access paths. </p>
|
|||
|
<p>However, if the system abnormally ended during the day, the access path
|
|||
|
to the smaller transaction file might need to be rebuilt. Still, the access
|
|||
|
path to the large history file, being read-only for most of the day, would
|
|||
|
rarely be unsynchronized with its data. Therefore, you reduce the chance of
|
|||
|
rebuilding this access path.</p>
|
|||
|
<p>Consider the trade-off between using a file design to reduce access path
|
|||
|
rebuilding time and using system-supplied functions like access path journaling.
|
|||
|
The above file design might require a more complex application design. After
|
|||
|
evaluating your situation, you might decide to use system-supplied functions
|
|||
|
like journaling your access paths rather than design applications that are
|
|||
|
more complex.</p>
|
|||
|
</div>
|
|||
|
<div>
|
|||
|
<div class="familylinks">
|
|||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbaforzahfpro.htm" title="Rebuilding a database access path might take as much as one minute for every 10 000 records. But some factors might affect the time estimate for rebuilding access paths.">Rebuild access paths</a></div>
|
|||
|
</div>
|
|||
|
</div>
|
|||
|
</body>
|
|||
|
</html>
|