59 lines
3.7 KiB
HTML
59 lines
3.7 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="Design tables to reduce index rebuilding time" />
|
||
|
|
<meta name="abstract" content="Table design can also help reduce index recovery time." />
|
||
|
|
<meta name="description" content="Table design can also help reduce index recovery time." />
|
||
|
|
<meta name="DC.subject" content="index, table design considerations, database recovery, reducing index rebuilding time" />
|
||
|
|
<meta name="keywords" content="index, table design considerations, database recovery, reducing index rebuilding time" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1rcvjrn.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="rbal1tblindex" />
|
||
|
|
<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 tables to reduce index rebuilding time</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbal1tblindex"><a name="rbal1tblindex"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Design tables to reduce index rebuilding time</h1>
|
||
|
|
<div><p>Table design can also help reduce index recovery time.</p>
|
||
|
|
<div class="section"><p>For example, you can divide a large master table into a history
|
||
|
|
table and a transaction table. The transaction table is then used for adding
|
||
|
|
new data and the history table is used for inquiry only. Each day, you can
|
||
|
|
merge the transaction data into the history table and then clear
|
||
|
|
the transaction file for the next day's data. With this design, the time to
|
||
|
|
rebuild indexes can be shortened, because if the server abnormally ends during
|
||
|
|
the day, the index to the smaller transaction table might need to be rebuilt.
|
||
|
|
However, because the index to the large history table, is read-only for most
|
||
|
|
of the day, it might not be out of synchronization with its data, and might
|
||
|
|
not have to be rebuilt.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>Consider the trade-off between using table design
|
||
|
|
to reduce index rebuilding time and using server-supplied functions like access
|
||
|
|
path journaling. The table design described in the previous paragraph might
|
||
|
|
require a more complex application design. After evaluating your situation,
|
||
|
|
you can decide to use server-supplied functions like access path journaling
|
||
|
|
rather than design more complex applications.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal1rcvjrn.htm" title="Journal management can be used as a part of the backup and recovery strategy for relational databases and indexes.">Journal management for distributed relational databases</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|