November 22, 2007 at 10:28 am
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
April 14, 2011 at 11:00 pm
You will get better and easy explanation over here:
http://dotnetpeoples.blogspot.com/2011/04/difference-between-delete-and-truncate.html
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy