SQL/MX Release 2.0 Best Practices

Database Sizing Considerations 27
clause is omitted from the CREATE TABLE statement, table creation defaults to the volume from which
NonStop SQL/MX was started, which could be an unaudited volume. Some tools, like MicroStrategy, allow
you to set a preference to append information to an SQL statement. You could use this capability to add
the location clause. Not all tools allow this use. However, you can use this workaround:
Add a default location through MXCS:
Name: _DEFAULTS
Value: class defaults, volume $<vol>.<subvol>
This action forces all tables created through ODBC to be created in the defined volume, with the
subvolume dependent on the schema subvolume.
Starting with SQL/MX Release 2.1.0 (SPR ABU), a new CONTROL QUERY DEFAULT called
DDL_DEFAULT_LOCATIONS is available. This default permits defining a default location for tables and
indexes created without a LOCATION clause.