94 lines
6.3 KiB
HTML
94 lines
6.3 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="Network considerations for a distributed relational database" />
|
||
|
|
<meta name="abstract" content="The design of a network directly affects the performance of a distributed relational database." />
|
||
|
|
<meta name="description" content="The design of a network directly affects the performance of a distributed relational database." />
|
||
|
|
<meta name="DC.subject" content="network, requirements, considerations, ASP group, use, location, definition, user database, association with 'location', independent ASP, configuring with" />
|
||
|
|
<meta name="keywords" content="network, requirements, considerations, ASP group, use, location, definition, user database, association with 'location', independent ASP, configuring with" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1desappnet.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../books/sc415406.pdf" />
|
||
|
|
<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="rbal1networkconsid" />
|
||
|
|
<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>Network considerations for a distributed relational database</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbal1networkconsid"><a name="rbal1networkconsid"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Network considerations for a distributed relational database</h1>
|
||
|
|
<div><p>The design of a network directly affects the performance of a distributed
|
||
|
|
relational database.</p>
|
||
|
|
<div class="section"><p>To properly design a distributed relational database that works
|
||
|
|
well with a particular network, do the following things:</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><ul><li>Because the line speed can be very important to application performance,
|
||
|
|
provide sufficient capacity at the appropriate places in the network to achieve
|
||
|
|
efficient performance to the main distributed relational database applications. </li>
|
||
|
|
<li>Evaluate the available communication hardware and software and, if necessary,
|
||
|
|
your ability to upgrade.</li>
|
||
|
|
<li>For Advanced Program-to-Program Communication (APPC) connections, consider
|
||
|
|
the session limits and conversation limits specified when the network is defined.</li>
|
||
|
|
<li>Identify the hardware, software, and communication equipment needed (for
|
||
|
|
both test and production environments), and the best configuration of the
|
||
|
|
equipment for a distributed relational database network.</li>
|
||
|
|
<li>Consider the skills that are necessary to support TCP/IP as opposed to
|
||
|
|
those that are necessary to support APPC.</li>
|
||
|
|
<li>Take into consideration the initial service level agreements with end
|
||
|
|
user groups (such as what response time to expect for a given distributed
|
||
|
|
relational database application), and strategies for monitoring and tuning
|
||
|
|
the actual service provided.</li>
|
||
|
|
<li>Understand that you cannot use an APPC-protected DUW conversation
|
||
|
|
to connect to a database from an application requester (AR) which has been
|
||
|
|
set to an auxiliary storage pool (ASP) group for the current thread. </li>
|
||
|
|
<li>Develop a naming strategy for database objects in the distributed relational
|
||
|
|
database and for each location in the distributed relational database. A <dfn class="term">location</dfn> is
|
||
|
|
a specific relational database management system in an interconnected network
|
||
|
|
of relational database management systems that participate in distributed
|
||
|
|
relational database. A location in this sense can also be a user database
|
||
|
|
in a system configured with independent ASP groups. Consider the following
|
||
|
|
items when developing this strategy: <ul><li>The fully qualified name of an object in a distributed database has three
|
||
|
|
(rather than two) parts, and the highest-level qualifier identifies the location
|
||
|
|
of the object.</li>
|
||
|
|
<li>Each location in a distributed relational database should be given a unique
|
||
|
|
identification; each object in the database should also have a unique identification.
|
||
|
|
Duplicate identifications can cause serious problems. For example, duplicate
|
||
|
|
locations and object names might cause an application to connect to an unintended
|
||
|
|
remote database, and once connected, access an unintended object. Pay particular
|
||
|
|
attention to naming when networks are coupled.</li>
|
||
|
|
<li>Each location in a user database should also be given a unique identification.
|
||
|
|
If a user database on two different servers were to be named PAYROLL, there
|
||
|
|
would be a naming conflict if an application needed to access them both from
|
||
|
|
the same server. Note that when an independent ASP device is configured, the
|
||
|
|
user has an option to specify an RDB name for that device that is different
|
||
|
|
from the name of the ASP device itself. It is the RDB name associated with
|
||
|
|
the primary device in an ASP group by which that user database is known.</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal1desappnet.htm" title="Designing a distributed relational database involves making choices about applications, network considerations, and data considerations.">Design the application, network, and data for a distributed relational database</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="../books/sc415406.pdf " target="_blank">Communications Management PDF</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|