This post gives the most correct explanation of the delete and truncate operations. There is no free lunch either way!!. The concept of delete and truncate are very different. However in data protection stand point both work similer. Only difference is in the operational stand point where truncate frees lots of resources during its course. The comitted transactions can never be rolledback howver can be recovered to prior point in time using properly done full/diff/t-log backups. Even the log reader is not useful if the truncated/deleted data is changed by ‘following transactions’. So there must be some amount of redoing the work from users stand point. This can not be avoided and there is no possible logic which can avoid this situation. Hence this is the known limitation for ever.

Surprised not to see a single comment on this post.

- Durairaj Padhmanaban.