SQL/MX 3.1 Installation and Management Guide (H06.23+, J06.12+)

Managing an SQL/MX Distributed Database
HP NonStop SQL/MX Release 3.1 Installation and Management Guide—663852-001
13-18
Maintaining Local Autonomy in a Network for
SQL/MX Release 3.x
If CAT_1 and CAT_2 have few or no interrelations and if the database objects in the
two catalogs are rarely or never accessed by the same application programs or
queries, a configuration like that shown in Table 13-5
might make good sense. In this
configuration, an outage of node \A does not affect metadata access by applications
and queries that access object data in CAT_2. Likewise, an outage of node \B does not
prevent metadata access by applications and queries that access object data in
CAT_1.
If CAT_1 and CAT_2 are tightly interrelated and if most application programs and
queries access objects in both catalogs, the configuration described in Table 13-5
would instead look like the configuration shown in Table 13-6
.