SQL/MX Database Distribution White Paper

NonStop SQL/MX Database Distribution White Paper 22 November 2004
Hewlett-Packard Company – 529627-001 Page 10 of 12
Table Naming Changes
These alternatives require changes in table naming:
• Alternative 1: Application-Managed Node-Specific Names
• Alternative 2: Node-Specific Default Schema Names
• Alternative 3: Individual Catalogs
Compared to a nondistributed environment, Alternative 1 does not require any additional catalogs or
schemas. The other two alternatives do require additional catalogs or schemas.
Late Name Resolution Overhead
The overhead associated with late name resolution is an issue for these alternatives:
• Alternative 1: Application-Managed Node-Specific Names
• Alternative 3: Individual Catalogs
However, for Alternative 3, this issue can be avoided if modules are SQL compiled on each node.