<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Is TRUNCATE TABLE t same as DELETE FROM t?</title>
	<atom:link href="http://oraqa.com/2006/02/23/is-truncate-table-t-same-as-delete-from-t/feed/" rel="self" type="application/rss+xml" />
	<link>http://oraqa.com/2006/02/23/is-truncate-table-t-same-as-delete-from-t/</link>
	<description>Oracle Question and Answer</description>
	<lastBuildDate>Mon, 19 Dec 2011 14:21:07 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Karl Reitschuster</title>
		<link>http://oraqa.com/2006/02/23/is-truncate-table-t-same-as-delete-from-t/comment-page-1/#comment-146</link>
		<dc:creator>Karl Reitschuster</dc:creator>
		<pubDate>Fri, 24 Feb 2006 08:06:53 +0000</pubDate>
		<guid isPermaLink="false">http://oraqa.com/2006/02/23/is-truncate-table-t-same-as-delete-from-t/#comment-146</guid>
		<description>Hi Eddie thanks for posting; 
i would like to be stronger in my statements :

Truncate:
*is* faster than removing all rows with the DELETE statement 

Delete:
*is* slower than removing all rows with the TRUNCATE statement 


Additionally 
Delete ( the whole table ) causes a lot of IO on INDEX Segments, UNDO Blocks and Redo logs.

If you truncate a table and know that you will fill it again with almost the same amount of data 
there is a TRUNCATE TABLE [TABLE_NAME] REUSE STORAGE. All Extents remain allocated - a load of may rows is faster then.

Greetings
Karl</description>
		<content:encoded><![CDATA[<p>Hi Eddie thanks for posting;<br />
i would like to be stronger in my statements :</p>
<p>Truncate:<br />
*is* faster than removing all rows with the DELETE statement </p>
<p>Delete:<br />
*is* slower than removing all rows with the TRUNCATE statement </p>
<p>Additionally<br />
Delete ( the whole table ) causes a lot of IO on INDEX Segments, UNDO Blocks and Redo logs.</p>
<p>If you truncate a table and know that you will fill it again with almost the same amount of data<br />
there is a TRUNCATE TABLE [TABLE_NAME] REUSE STORAGE. All Extents remain allocated &#8211; a load of may rows is faster then.</p>
<p>Greetings<br />
Karl</p>
]]></content:encoded>
	</item>
</channel>
</rss>

