ibm-information-center/dist/eclipse/plugins/i5OS.ic.ddp_5.4.0.1/rbal1saveindex.htm

63 lines
4.3 KiB
HTML
Raw Permalink Normal View History

2024-04-02 14:02:31 +00:00
<?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="Save and restore indexes in the distributed relational database environment" />
<meta name="abstract" content="Restoring an SQL index can be faster than rebuilding it. Although times vary depending on a number of factors, rebuilding a database index takes approximately one minute for every 10 000 rows." />
<meta name="description" content="Restoring an SQL index can be faster than rebuilding it. Although times vary depending on a number of factors, rebuilding a database index takes approximately one minute for every 10 000 rows." />
<meta name="DC.subject" content="saving, indexes, restoring, index, saving and restoring" />
<meta name="keywords" content="saving, indexes, restoring, index, saving and restoring" />
<meta name="DC.Relation" scheme="URI" content="rbal1saverestore.htm" />
<meta name="DC.Relation" scheme="URI" content="../rzahg/rzahgbackup.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="rbal1saveindex" />
<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>Save and restore indexes in the distributed relational database environment</title>
</head>
<body id="rbal1saveindex"><a name="rbal1saveindex"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Save and restore indexes in the distributed relational database environment</h1>
<div><p>Restoring an SQL index can be faster than rebuilding it. Although
times vary depending on a number of factors, rebuilding a database index takes
approximately one minute for every 10 000 rows.</p>
<div class="section"><p>After restoring the index, the table might need to be brought
up to date by applying the latest journal changes (depending on whether journaling
is active). Even with this additional recovery time, you might find it faster
to restore indexes rather than to rebuild them.</p>
</div>
<div class="section"><p>The server ensures the integrity of an index before you can use
it. If the server determines that the index is unusable, the server attempts
to recover it. You can control when an index will be recovered. If the server
ends abnormally, during the next IPL the server automatically lists those
tables requiring index or view recovery. You can decide whether to rebuild
the index or to attempt to recover it at one of the following times: </p>
<ul><li>During the IPL</li>
<li>After the IPL</li>
<li>When the table is first used</li>
</ul>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal1saverestore.htm" title="Saving and restoring data and programs allows recovery from a program or server failure, exchange of information between servers, or storage of objects or data offline. A sound backup policy at each server in the distributed relational database network ensures that a server can be restored and made available to network users quickly in the event of a problem.">Save and restore processing for a distributed relational database</a></div>
</div>
<div class="relconcepts"><strong>Related concepts</strong><br />
<div><a href="../rzahg/rzahgbackup.htm">Backup and recovery</a></div>
</div>
</div>
</body>
</html>