?
Solved

Delete and truncate comparison

Posted on 2015-01-19
4
Medium Priority
?
141 Views
Last Modified: 2015-01-20
Please add your take on the following statements:

1. Some drop a table and recreate it because it is faster than deleting it.

2. Delete, deletes the data based on where clause from data pages (?) thus lowers the performance because disk fragmentation that occurs during the delete operation. SQL Server rebuilds the indexes and defrags disk later but not right-away.

3. Truncate deletes data the data and deals with data fragmentation right away (slows SQL Server engine at that time)
0
Comment
Question by:Mike Eghtebas
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
4 Comments
 
LVL 66

Accepted Solution

by:
Jim Horn earned 1000 total points
ID: 40558714

1.

Correct, although TRUNCATE will be faster than DELETE ALL, and you may blow away privs on an object by doing a DROP and CREATE vs. keeping it alive with a TRUNCATE.

2.

Decrease speed as it has to process a WHERE clause, yes, everything else I'll defer to the DBA experts here.

3.

TRUNCATE blows away all pages, plus it's only minimally logged (if it wasn't it wouldn't be able to particiate in a transaction), so it's much faster than DELETE.
0
 
LVL 69

Assisted Solution

by:Scott Pletcher
Scott Pletcher earned 600 total points
ID: 40558715
1.  Not logical.  It would be faster to just truncate the table.

2.  Delete would not have a WHERE clause if you're trying to mimic a truncate.  The big difference is that Delete logs each row, while Truncate only logs each page.

3.  Truncate does the remove the data right away and eliminate fragmentation.  But it does not "slow" the SQL engine.  The pages to be deleted must be logged regardless of the method used to delete them.
0
 
LVL 69

Assisted Solution

by:Scott Pletcher
Scott Pletcher earned 600 total points
ID: 40558729
A WHERE clause on a DELETE could speed up the DELETEs considerably, since it could reduce, possibly drastically, the number of rows that needed DELETEd.

I'm not sure that TRUNCATE is technically "minimally logged".  At any rate, if you are in full recovery model, it can't be anyway.
0
 
LVL 8

Assisted Solution

by:Dung Dinh
Dung Dinh earned 400 total points
ID: 40559032
Some more information about comparison between DELETE and TRUNCATE
https://databaseskills.wordpress.com/2014/05/20/compare-truncate-and-delete-statement/
0

Featured Post

Ransomware: The New Cyber Threat & How to Stop It

This infographic explains ransomware, type of malware that blocks access to your files or your systems and holds them hostage until a ransom is paid. It also examines the different types of ransomware and explains what you can do to thwart this sinister online threat.  

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Why is this different from all of the other step by step guides?  Because I make a living as a DBA and not as a writer and I lived through this experience. Defining the name: When I talk to people they say different names on this subject stuff l…
I have a large data set and a SSIS package. How can I load this file in multi threading?
This videos aims to give the viewer a basic demonstration of how a user can query current session information by using the SYS_CONTEXT function
Viewers will learn how to use the INSERT statement to insert data into their tables. It will also introduce the NULL statement, to show them what happens when no value is giving for any given column.
Suggested Courses

777 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question