Hello Prashant,
We frequently do massive migrations from one database to another.
Typical migrations consisting of reading in large textbased data and copying/converting the resulting tabels to a destination database multiple times.
There is a group in our company favoring drop/create table statements prior to the last step in the destination database and after copying/converting the data , creating the related indices. Another group ( in case there is a limited number of indices) favors truncating destination tables.
I belong to the first group, telling the second group 'truncation is destroying the indices' implicitly telling that the resulting indices after copying data maybe corrupt.
Is what i say true?
Thanks and kind regards,
Christian
PS. This wasnt meant as a new topic, sorry