Moving a customer from HVR5 to HVR6 - The team had scripts created on HVR5 to adapt tables across 90 channels. To do this, they were directly inserting rows into e.g. HVR_COLUMN to introduce new columns in their tables.
 
This is strictly forbidden on HVR6, and the obvious route to go is by enabling AdaptDDL or running hvradapt. The team has an elaborate design where the same table is added to channels multiple times, and this is a non-negotiable design element. Neither AdaptDDL, nor hvradapt support this and we get errors. The team would prefer a scripted solution using hvradapt, e.g. by introducing a flag that allows hvradapt to run on such a channel and update the column/datatype information even if the table names are duplicated within the channel.