<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://sqlblog.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>TSQL Tuesday #11:Rolling Back TRUNCATE TABLE</title><link>http://sqlblog.com/blogs/kalen_delaney/archive/2010/10/12/tsql-tuesday-11-rolling-back-truncate-table.aspx</link><description>“It ain't what people don't know that hurts them it's what they know that ain't so” -- commonly attributed to Mark Twain SQL Server has been around for a long time now, and people who learn one version well sometimes have monumental task when a new version</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.1)</generator><item><title>re: TSQL Tuesday #11:Rolling Back TRUNCATE TABLE</title><link>http://sqlblog.com/blogs/kalen_delaney/archive/2010/10/12/tsql-tuesday-11-rolling-back-truncate-table.aspx#29347</link><pubDate>Tue, 12 Oct 2010 21:39:54 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:29347</guid><dc:creator>James Luetkehoelter</dc:creator><description>&lt;p&gt;A very wise and sagacious post as usual. I find the same thing (the misconsception amongst active DBAs) with TRUNCATE or minimally logged transactions altogether. Hey, that would make a great 2-3 hour talk. That or hobts (Sorry Kalen, couldn't resist - don't blacklist me!).&lt;/p&gt;
</description></item><item><title>re: TSQL Tuesday #11:Rolling Back TRUNCATE TABLE</title><link>http://sqlblog.com/blogs/kalen_delaney/archive/2010/10/12/tsql-tuesday-11-rolling-back-truncate-table.aspx#29394</link><pubDate>Thu, 14 Oct 2010 17:22:03 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:29394</guid><dc:creator>mbourgon</dc:creator><description>&lt;p&gt;Ha! Awesome. &amp;nbsp;I've actually used that before (doing a truncate within a transaction), stunned that it worked that way. &amp;nbsp;Thanks for the reminder.&lt;/p&gt;
</description></item><item><title>re: TSQL Tuesday #11:Rolling Back TRUNCATE TABLE</title><link>http://sqlblog.com/blogs/kalen_delaney/archive/2010/10/12/tsql-tuesday-11-rolling-back-truncate-table.aspx#29509</link><pubDate>Tue, 19 Oct 2010 20:38:42 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:29509</guid><dc:creator>arjanf</dc:creator><description>&lt;p&gt;Hi Kalen,&lt;/p&gt;
&lt;p&gt;I did deliver some comment on a linked in discussion a while ago based on the same subject.&lt;/p&gt;
&lt;p&gt;I believe that when you do a truncation on a table with an Identity(1,1) column in it the identity is kept out of the transaction. This means that you could mess up your identity when you use it by mistake on such table. Is this correct?&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Arjan&lt;/p&gt;
</description></item><item><title>re: TSQL Tuesday #11:Rolling Back TRUNCATE TABLE</title><link>http://sqlblog.com/blogs/kalen_delaney/archive/2010/10/12/tsql-tuesday-11-rolling-back-truncate-table.aspx#29905</link><pubDate>Wed, 27 Oct 2010 20:47:27 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:29905</guid><dc:creator>Dale</dc:creator><description>&lt;p&gt;But if the transaction is committed, then you cannot roll it back, correct?&lt;/p&gt;
</description></item><item><title>re: TSQL Tuesday #11:Rolling Back TRUNCATE TABLE</title><link>http://sqlblog.com/blogs/kalen_delaney/archive/2010/10/12/tsql-tuesday-11-rolling-back-truncate-table.aspx#29911</link><pubDate>Wed, 27 Oct 2010 23:19:04 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:29911</guid><dc:creator>Kalen Delaney</dc:creator><description>&lt;p&gt;Arjan... what do you mean by 'mess up? There is no way that part of a row could be 'out' of the transaction. When you truncate a table with identity, the identity is reset. &lt;/p&gt;
&lt;p&gt;Dale... COMMIT is the opposite of ROLLBACK. If you do one, you can't do the other.&lt;/p&gt;
</description></item><item><title>re: TSQL Tuesday #11:Rolling Back TRUNCATE TABLE</title><link>http://sqlblog.com/blogs/kalen_delaney/archive/2010/10/12/tsql-tuesday-11-rolling-back-truncate-table.aspx#30059</link><pubDate>Mon, 01 Nov 2010 18:11:27 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:30059</guid><dc:creator>Paul Williams</dc:creator><description>&lt;p&gt;Thank you for logging this. &amp;nbsp;I never realized TRUNCATE TABLE could be rolled back.&lt;/p&gt;
</description></item><item><title>re: TSQL Tuesday #11:Rolling Back TRUNCATE TABLE</title><link>http://sqlblog.com/blogs/kalen_delaney/archive/2010/10/12/tsql-tuesday-11-rolling-back-truncate-table.aspx#45307</link><pubDate>Sat, 22 Sep 2012 08:08:48 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:45307</guid><dc:creator>Raj</dc:creator><description>&lt;p&gt;Kalen,&lt;/p&gt;
&lt;p&gt;suppose we have done commit truncate table ..but can we recover that trucate table through &amp;nbsp;transactional logged backup ? as we can do that for deleted rows ...&lt;/p&gt;
</description></item><item><title>re: TSQL Tuesday #11:Rolling Back TRUNCATE TABLE</title><link>http://sqlblog.com/blogs/kalen_delaney/archive/2010/10/12/tsql-tuesday-11-rolling-back-truncate-table.aspx#45308</link><pubDate>Sun, 23 Sep 2012 00:33:43 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:45308</guid><dc:creator>Kalen Delaney</dc:creator><description>&lt;p&gt;Hi Raj&lt;/p&gt;
&lt;p&gt;We can use a log backup to recover any changes by just restoring to a time BEFORE the change took place, whether it's a delete, truncate or drop table, it doesn't matter. The restore does not actually undo anything.. it just brings the database back to a point before you removed the data. &lt;/p&gt;
&lt;p&gt;~Kalen&lt;/p&gt;
</description></item></channel></rss>