|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Tuesday, November 27, 2007 4:30 AM
Points: 1,
Visits: 5
|
|
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
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Wednesday, April 20, 2011 11:40 PM
Points: 6,
Visits: 2
|
|
You will get better and easy explanation over here: http://dotnetpeoples.blogspot.com/2011/04/difference-between-delete-and-truncate.html
|
|
|
|