Kbase P125643: What schema changes will cause a lot of BI / AI growth?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/4/2009 |
|
Status: Verified
GOAL:
What schema changes will cause a lot of BI / AI growth?
GOAL:
Will adding/deleting/modifying fields cause BI / AI growth?
GOAL:
Will adding indexes cause BI / AI growth?
GOAL:
Does Schema Versioning stop all BI / AI growth during schema updates?
FACT(s) (Environment):
Progress 9.x
OpenEdge 10.x
All Supported Operating Systems
FIX:
In Progress version 9, Schema Versioning was introduced.
Schema Versioning works for all field-level changes: adding/removing/editing a field, all fall into the Schema Versioning.
This is achieved by adding a schema-version [hidden] field to each record. When the schema is changed, the schema version is increased by 1 and any new records created will have the new version stored in the hidden field, older records are left untouched.
When reading records from the database, the schema version of the table is checked with the schema version of the record, and if it's not the same then the physical layout of the record is adjusted to match the latest version.
The advantage of Schema Versioning in v9 and oe10 is that only deleting and adding an [active] index will generate a lot of bi / ai activity; field-level changes cause no big activity.