Hi,
We are presently use the "using index" clause when create PK and AK constraints. This enables to create an index in a separate tablespace. This works when generating DDL.
However, when reserse-engineering a database created from a model that contains the "using index" clause, the reverse-engineered model does not contain the "using index" clase. This means I cannot update the model via a merge without removing the "using index" clause, which would prevent me from creating further DDL from the model
Is there a way to reverse-engineer the "using index" clause or to create DDL in a way that does not require the clause such that the index can be placed in a specified tablespace?
Thanks,
Greg