Kbase P77947: Is there a way to know the progression of a schema change
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
4/23/2004 |
|
Status: Unverified
GOAL:
Is there a way to know the progression of a schema change
GOAL:
What is the impact of aborting a schema change
FIX:
No there is no way to know about the progression of a schema change.
The best way to make it fast is to compute it on the database server itself with a shared memory connection (without -S, providing full path of the Database .db file) rather than from a client server session. You might even want to define new indexes with a status of inactive and build them later with a proutil idxbuild.
At last, aborting a schema change will result in a transaction rollback, which may take as long as the schema change has been running.