Where a table lives on disk is a DBA decision that the schema should carry, not a script someone runs afterwards. This release lets the schema model name the storage space for tables, large-object columns and indexes, and compiles it into the DDL.
Placement in the model
- Large objects by pattern A layout rule matches table names to a dbspace for their CLOB columns, emitted as an IN clause on the column; the space is checked for existence first.
- Indexes placed An index names its dbspace as a table does.
- Layouts recorded A server layout table in the configuration database records the placement per database server.
- Unique with nulls A unique index may declare that multiple null values are allowed, where the engine supports it.
Two years later the storage advisor reads the same model to propose a layout for the largest tables. This is the release that made placement something the model could express.