SQL/MX Database Distribution White Paper

NonStop SQL/MX Database Distribution White Paper 22 November 2004
Hewlett-Packard Company – 529627-001 Page 11 of 12
Here’s another way to compare alternatives:
Alternative 1:
Application-Managed
Node-Specific Names
Alternative 2:
Node-Specific
Default Schema
Names
Alternative 3:
Individual
Catalogs
Alternative 4:
Replication Through
Partitioning
Apart from table
names in queries,
can source code
changes be avoided?
No Yes Yes No
Can database design
changes be avoided?
Yes Yes Yes No
Can module
compilation on each
node be avoided?
Yes No Yes (*) Yes
Are individual
copies globally
visible?
Yes Yes No Yes
Can DB name
changes be avoided?
No No No Yes
Can late name
resolution overhead
be avoided?
No Yes Yes (*) Yes
(*) One of these will be “Yes,” the other one will be “No.”
2.2.6. Summary
Unfortunately, there is no one-size-fits-all recommendation, because the pros and cons are different for the
individual alternatives, as can be seen in the previous table.
Alternative 4 differs from the other three alternatives in two significant ways:
a) Alternative 4 introduces artificial database design changes.