I am comparing two databases. One is on Development and the other on Test environments. While the application system has been in development the number of data rows have not been large but now that it's time to start system testing the planned number of rows will increase to a defined number that will stress test the application.
How do I tell RC/Migrator to resize the tablespaces and indexes? I have already migrated an initial copy of the development objects to test and have been doing comparisons at intervals to update the test objects. Do I have to migrate the database from scratch and drop the test database?
Release: R20
Component: RCC, RCM
RC/Migrator Space Calculator feature is able to adjust the Primary and Secondary quantities for tablespaces and indexes. The specific number of expected data rows are provided for this calculation by the user.
No, the database does not have to be migrated again or dropped.
This resizing can be done either during a migration or compare in a similar fashion.
Let's assume you know for a fact how many records will be loaded to each test table. This is already decided and all that has to be done is for the primary and secondary quantities of those tablespaces and indexes to be adjusted accordingly.
Resizing in a MIGRATION strategy can be done with these steps:
For Tablespaces
For Indexes
When finished PF3 back to Strategy Services and perform the Analysis. The adjusted quantities will be generated in the DDL for the tablespace and/or indexes.
Resizing in a COMPARE strategy can be done with these steps:
For Tablespaces
For Indexes
When finished PF3 back to Strategy Services and perform the Analysis. The adjusted quantities will be generated in the DDL for the tablespace and/or indexes.