Answer by Grant Fritchey
In terms of performance, truncate is minimally logged and delete is logged for the transaction, regardless of the recovery model of the database. With that in mind, yes, there is still a difference and...
View ArticleAnswer by TimothyAWiseman
+1 to Grant, but also remember that truncate resets an identity column and delete will not. Additionally, truncate will not activate on delete triggers if you are using those.
View ArticleAnswer by Blackhawk-17
If you want to see an in-depth explanation of the differences in logging that Grant refers to head over to SSC.Also, TRUNCATE uses a table lock rather than the row locks that DELETE uses. You can also...
View ArticleAnswer by Grant Fritchey
In terms of performance, truncate is minimally logged and delete is logged for the transaction, regardless of the recovery model of the database. With that in mind, yes, there is still a difference and...
View ArticleAnswer by TimothyAWiseman
+1 to Grant, but also remember that truncate resets an identity column and delete will not. Additionally, truncate will not activate on delete triggers if you are using those.
View ArticleAnswer by Blackhawk-17
If you want to see an in-depth explanation of the differences in logging that Grant refers to head over to SSC.Also, TRUNCATE uses a table lock rather than the row locks that DELETE uses. You can also...
View Article