August 25, 2011 at 6:16 am
Basics is just what I need. My SQL career is still an infant. 😛
September 5, 2011 at 4:43 am
Interesting and somewhat horrifying - up to now, 43% said delete was not logged, which is amazing considering how much discussion of that there has been on SQLServerCentral.com; and more tha 50% got it wrong that way or some other way. 6% chosing "delete resets ID, truncate does not" is crazy, I hope these guys never use identity columns because if they believe that nonsense they are going to make some really horrible mistakes, like thinking that if their table behaves like a stack IDs will always be contiguous, which can cause lots of lovely bugs.
I too, agree with Tom. The truncate is great if you know what you are doing because it saves time but it is one of those commands that can be horrifying if used without a good understanding of where you expect it to go.
Delete the records in a table, and you can get them back with a good recovery program. Truncate them and you better hope you have a good backup because recovery is not an option. And then there is that truly annoying ID issue...
Jamie
October 13, 2011 at 11:33 am
"Faster in performance wise, because it doesn’t keep any logs" ??????
so ?
October 13, 2011 at 11:37 am
So that if you accidently have the wrong server up and you delete records from that server and not the one intended, there is still a path to recovery. Instead of showing the record deleted in the log, it removes the transaction from the log which makes it faster.
Jamie
November 8, 2011 at 3:05 pm
I also have posted 3 options and I thought I was right!! Is there an ambiguity to this question and the answers or I really need to go back to the basics :-P:-D:w00t:
(see attached)
Cheers,
John Esraelo
March 2, 2012 at 3:34 pm
Great question and review of the basics.
Thanks.
January 24, 2013 at 9:12 pm
simple n easy question:)
Viewing 7 posts - 46 through 52 (of 52 total)
You must be logged in to reply to this topic. Login to reply