77 lines
5.6 KiB
HTML
77 lines
5.6 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="Planning and design" />
|
|
<meta name="abstract" content="The first requirement for the successful operation of a distributed relational database is thorough planning. You must consider the needs and goals of your enterprise when making the decision to use a distributed relational database." />
|
|
<meta name="description" content="The first requirement for the successful operation of a distributed relational database is thorough planning. You must consider the needs and goals of your enterprise when making the decision to use a distributed relational database." />
|
|
<meta name="DC.subject" content="planning for distributed relational database, design for distributed relational database" />
|
|
<meta name="keywords" content="planning for distributed relational database, design for distributed relational database" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1kickoff.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1idyourneeds.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1desappnet.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1managestrat.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1improveviadata.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="rbal1plan" />
|
|
<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>Planning and design</title>
|
|
</head>
|
|
<body id="rbal1plan"><a name="rbal1plan"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Planning and design</h1>
|
|
<div><p>The first requirement for the successful operation of a distributed
|
|
relational database is thorough planning. You must consider the needs and
|
|
goals of your enterprise when making the decision to use a distributed
|
|
relational database. </p>
|
|
<p>How you code an application program, where it resides in relation to the
|
|
data, and the network design that connects application programs to data are
|
|
all important design considerations. </p>
|
|
<p> Database design in a distributed relational database is more critical
|
|
than when dealing with just one <span class="keyword">iSeries™</span> relational
|
|
database. With more than one <span class="keyword">iSeries server</span> to
|
|
consider, you must develop a consistent management strategy across the network.
|
|
The following operations require particular attention when forming your strategy: </p>
|
|
<ul><li>General operations</li>
|
|
<li>Networking protocol</li>
|
|
<li>System security</li>
|
|
<li>Accounting</li>
|
|
<li>Problem analysis</li>
|
|
<li>Backup and recovery processes</li>
|
|
</ul>
|
|
<p>To prepare for a distributed relational database, you must understand both
|
|
the needs of the business and relational database technology.</p>
|
|
</div>
|
|
<div>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="rbal1idyourneeds.htm">Identify your needs and expectations for a distributed relational database</a></strong><br />
|
|
Consider these items when analyzing your needs and expectations of a distributed relational database.</li>
|
|
<li class="ulchildlink"><strong><a href="rbal1desappnet.htm">Design the application, network, and data for a distributed relational database</a></strong><br />
|
|
Designing a distributed relational database involves making choices about applications, network considerations, and data considerations.</li>
|
|
<li class="ulchildlink"><strong><a href="rbal1managestrat.htm">Develop a management strategy for a distributed relational database</a></strong><br />
|
|
When you are managing a distributed relational database, keep these strategies in mind.</li>
|
|
</ul>
|
|
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal1kickoff.htm" title="Distributed database programming describes the distributed relational database management portion of the i5/OS licensed program. Distributed relational database management provides applications with access to data that is external to the applications and typically located across a network of computers.">Distributed database programming</a></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><a href="rbal1improveviadata.htm" title="Distributed relational database performance is affected by the overall design of the database. The location of distributed data, the level of commitment control you use, and the design of your SQL indexes all affect performance.">Improve distributed relational database performance through the database</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |