-
Type:
Feature Request
-
Resolution: Unresolved
-
Priority:
L3 - Default
-
None
-
Affects Version/s: None
-
Component/s: engine
User Story (Required on creation):
Tablespaces are a concept in Oracle to physically organize database objects (e.g. tables, indexes), e.g. see https://docs.oracle.com/database/121/ADMQS/GUID-F05EE514-FFC6-4E86-A592-802BA5A49254.htm#ADMQS12053. Some administrators want to use different tablespaces for all tables and all indexes (for example, the size of a tablespace can be easily monitored and by separating tables and indexes, administrators can track clearly how large the indexes become independent of the tables).
Functional Requirements (Required before implementation):
- When running a DDL script, I can set a parameter for the tablespace that is used to create tables and another parameter that is used as the tablespace for the indexes
- If the parameters are not set, then the default tablespace is used (=> same behavior as with the current scripts)
Technical Requirements (Required before implementation):
Limitations of Scope (Optional):
Hints (Optional):
- When we implement
CAM-1038, this may either already come out of the box or the solution may look a little different (e.g. see https://stackoverflow.com/questions/62169379/how-to-use-different-tablespaces-for-tables-and-indexes-with-liquibase-in-java for how this can be achieved with Liquibase)