Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Difference between truncate and delete Expand / Collapse
Author
Message
Posted Thursday, November 22, 2007 10:28 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum 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
Post #425035
Posted Thursday, April 14, 2011 11:00 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum 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
Post #1093903
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse