RealHeavyDude
Well-Known Member
Did anybody encounter tables without a single index yet in an OpenEdge database?
By chance, only after the migration, I stumbled over 15 indexes which were residing in the schema area on the target system where they reside in the respective type II storage areas in the source system. Dammit - how can this happen?
Luckily - these are test systems with the same schema and roughly the same amount of data like the production systems.
It turns out, those 15 indexes are all named "default" and are missing from the DF file that has been dumped on the source system - meaning there are 15 tables in the source database which do not have a single index associated with them in the DF ...
So, when the DF was loaded on the target system those "default" indexes have been been created automagically along the way - and, as a bonus - reside in the schema area, with all sorts of negative side effects.
As a result I need to find a desperate solution to enhance the load script to cope with the index move of those "default" indexes before the binary load is invoked ...
Sometimes I really feel like a garbage man. Why in the world would anybody be so irresponsible to have a database table with no index ( not even speaking about uniqueness )?
By chance, only after the migration, I stumbled over 15 indexes which were residing in the schema area on the target system where they reside in the respective type II storage areas in the source system. Dammit - how can this happen?
Luckily - these are test systems with the same schema and roughly the same amount of data like the production systems.
It turns out, those 15 indexes are all named "default" and are missing from the DF file that has been dumped on the source system - meaning there are 15 tables in the source database which do not have a single index associated with them in the DF ...
So, when the DF was loaded on the target system those "default" indexes have been been created automagically along the way - and, as a bonus - reside in the schema area, with all sorts of negative side effects.
As a result I need to find a desperate solution to enhance the load script to cope with the index move of those "default" indexes before the binary load is invoked ...
Sometimes I really feel like a garbage man. Why in the world would anybody be so irresponsible to have a database table with no index ( not even speaking about uniqueness )?