<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: SQL SERVER &#8211; CDC and TRUNCATE &#8211; Cannot truncate table because it is published for replication or enabled for Change Data Capture</title>
	<atom:link href="http://blog.sqlauthority.com/2009/12/25/sql-server-cdc-and-truncate-cannot-truncate-table-because-it-is-published-for-replication-or-enabled-for-change-data-capture/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.sqlauthority.com/2009/12/25/sql-server-cdc-and-truncate-cannot-truncate-table-because-it-is-published-for-replication-or-enabled-for-change-data-capture/</link>
	<description>Personal Notes of Pinal Dave</description>
	<lastBuildDate>Fri, 17 May 2013 15:26:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Chuck</title>
		<link>http://blog.sqlauthority.com/2009/12/25/sql-server-cdc-and-truncate-cannot-truncate-table-because-it-is-published-for-replication-or-enabled-for-change-data-capture/#comment-457924</link>
		<dc:creator><![CDATA[Chuck]]></dc:creator>
		<pubDate>Wed, 17 Apr 2013 11:49:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7625#comment-457924</guid>
		<description><![CDATA[Truncate is most certainly logged. If it were not, no database that had a table truncated could ever be restored and recovered. Log shipping and mirroring  would break as well as any other feature that depends on the transaction log or transaction log backups. 

Don&#039;t believe me?: Create a database, create and populate a table, take a full backup, truncate the table, table a log backup. Now restore the full backup with norecovery, then the log backup with recovery. Query the table and you&#039;ll find it has no rows. The truncate was logged. 

There must be some other reason why Microsoft doesn&#039;t allow truncate along with CDC or CT but its not because the operation isn&#039;t logged. It is.]]></description>
		<content:encoded><![CDATA[<p>Truncate is most certainly logged. If it were not, no database that had a table truncated could ever be restored and recovered. Log shipping and mirroring  would break as well as any other feature that depends on the transaction log or transaction log backups. </p>
<p>Don&#8217;t believe me?: Create a database, create and populate a table, take a full backup, truncate the table, table a log backup. Now restore the full backup with norecovery, then the log backup with recovery. Query the table and you&#8217;ll find it has no rows. The truncate was logged. </p>
<p>There must be some other reason why Microsoft doesn&#8217;t allow truncate along with CDC or CT but its not because the operation isn&#8217;t logged. It is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pundarik Rawal</title>
		<link>http://blog.sqlauthority.com/2009/12/25/sql-server-cdc-and-truncate-cannot-truncate-table-because-it-is-published-for-replication-or-enabled-for-change-data-capture/#comment-455557</link>
		<dc:creator><![CDATA[Pundarik Rawal]]></dc:creator>
		<pubDate>Sun, 14 Apr 2013 03:03:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7625#comment-455557</guid>
		<description><![CDATA[no]]></description>
		<content:encoded><![CDATA[<p>no</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sanjeev</title>
		<link>http://blog.sqlauthority.com/2009/12/25/sql-server-cdc-and-truncate-cannot-truncate-table-because-it-is-published-for-replication-or-enabled-for-change-data-capture/#comment-422773</link>
		<dc:creator><![CDATA[Sanjeev]]></dc:creator>
		<pubDate>Sun, 17 Feb 2013 06:36:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7625#comment-422773</guid>
		<description><![CDATA[Have you got the reply for the question asked?]]></description>
		<content:encoded><![CDATA[<p>Have you got the reply for the question asked?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chuck</title>
		<link>http://blog.sqlauthority.com/2009/12/25/sql-server-cdc-and-truncate-cannot-truncate-table-because-it-is-published-for-replication-or-enabled-for-change-data-capture/#comment-409485</link>
		<dc:creator><![CDATA[Chuck]]></dc:creator>
		<pubDate>Fri, 18 Jan 2013 19:54:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7625#comment-409485</guid>
		<description><![CDATA[I know this is a really old thread, but what would be the problem with recording the update as a delete/insert for the purposes of CDC? Primary keys really are a special case.]]></description>
		<content:encoded><![CDATA[<p>I know this is a really old thread, but what would be the problem with recording the update as a delete/insert for the purposes of CDC? Primary keys really are a special case.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SQL SERVER &#8211; Weekly Series &#8211; Memory Lane &#8211; #009 &#171; SQL Server Journey with SQL Authority</title>
		<link>http://blog.sqlauthority.com/2009/12/25/sql-server-cdc-and-truncate-cannot-truncate-table-because-it-is-published-for-replication-or-enabled-for-change-data-capture/#comment-400677</link>
		<dc:creator><![CDATA[SQL SERVER &#8211; Weekly Series &#8211; Memory Lane &#8211; #009 &#171; SQL Server Journey with SQL Authority]]></dc:creator>
		<pubDate>Sat, 29 Dec 2012 01:31:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7625#comment-400677</guid>
		<description><![CDATA[[...] CDC and TRUNCATE – Cannot truncate table because it is published for replication or enabled for Ch... [...]]]></description>
		<content:encoded><![CDATA[<p>[...] CDC and TRUNCATE – Cannot truncate table because it is published for replication or enabled for Ch&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pundarik</title>
		<link>http://blog.sqlauthority.com/2009/12/25/sql-server-cdc-and-truncate-cannot-truncate-table-because-it-is-published-for-replication-or-enabled-for-change-data-capture/#comment-375441</link>
		<dc:creator><![CDATA[Pundarik]]></dc:creator>
		<pubDate>Sat, 17 Nov 2012 09:10:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7625#comment-375441</guid>
		<description><![CDATA[Sir i have question regarding that,
If we disable CDC and then re-enable, then we lose existing CDC tables that tracked changes up to the point of disabling CDC. How can we use both feature disable CDC but keep already tracked data?
Thx in advance ...pls ans ASAP.]]></description>
		<content:encoded><![CDATA[<p>Sir i have question regarding that,<br />
If we disable CDC and then re-enable, then we lose existing CDC tables that tracked changes up to the point of disabling CDC. How can we use both feature disable CDC but keep already tracked data?<br />
Thx in advance &#8230;pls ans ASAP.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rakesh hendre</title>
		<link>http://blog.sqlauthority.com/2009/12/25/sql-server-cdc-and-truncate-cannot-truncate-table-because-it-is-published-for-replication-or-enabled-for-change-data-capture/#comment-369566</link>
		<dc:creator><![CDATA[Rakesh hendre]]></dc:creator>
		<pubDate>Mon, 05 Nov 2012 09:57:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7625#comment-369566</guid>
		<description><![CDATA[Is there is any process for truncating the tablle which are published in the replication?? Becoz i am having more than 350 tables which are being used fore generating crystal reports . should have to truncated before running the report.. I am having 5 branches data collection so have to make publication of 5branches.. kindly give me the solution so that my table should be truncated...]]></description>
		<content:encoded><![CDATA[<p>Is there is any process for truncating the tablle which are published in the replication?? Becoz i am having more than 350 tables which are being used fore generating crystal reports . should have to truncated before running the report.. I am having 5 branches data collection so have to make publication of 5branches.. kindly give me the solution so that my table should be truncated&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SQL SERVER &#8211; A Quick Look at Logging and Ideas around Logging &#171; SQL Server Journey with SQL Authority</title>
		<link>http://blog.sqlauthority.com/2009/12/25/sql-server-cdc-and-truncate-cannot-truncate-table-because-it-is-published-for-replication-or-enabled-for-change-data-capture/#comment-300141</link>
		<dc:creator><![CDATA[SQL SERVER &#8211; A Quick Look at Logging and Ideas around Logging &#171; SQL Server Journey with SQL Authority]]></dc:creator>
		<pubDate>Tue, 12 Jun 2012 01:32:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7625#comment-300141</guid>
		<description><![CDATA[[...] CDC and TRUNCATE – Cannot truncate table because it is published for replication or enabled for Ch... [...]]]></description>
		<content:encoded><![CDATA[<p>[...] CDC and TRUNCATE – Cannot truncate table because it is published for replication or enabled for Ch&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: T</title>
		<link>http://blog.sqlauthority.com/2009/12/25/sql-server-cdc-and-truncate-cannot-truncate-table-because-it-is-published-for-replication-or-enabled-for-change-data-capture/#comment-127377</link>
		<dc:creator><![CDATA[T]]></dc:creator>
		<pubDate>Thu, 07 Apr 2011 13:49:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7625#comment-127377</guid>
		<description><![CDATA[If you disable CDC and then re-enable, then you lose existing CDC tables that tracked changes up to the point of disabling CDC. How can you disable future CDC but keep already tracked data?]]></description>
		<content:encoded><![CDATA[<p>If you disable CDC and then re-enable, then you lose existing CDC tables that tracked changes up to the point of disabling CDC. How can you disable future CDC but keep already tracked data?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lili</title>
		<link>http://blog.sqlauthority.com/2009/12/25/sql-server-cdc-and-truncate-cannot-truncate-table-because-it-is-published-for-replication-or-enabled-for-change-data-capture/#comment-97508</link>
		<dc:creator><![CDATA[lili]]></dc:creator>
		<pubDate>Wed, 03 Nov 2010 04:58:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7625#comment-97508</guid>
		<description><![CDATA[hi all.
we use cdc tables for store modified data in database and we can see those easily,but now we want to add host name 
and computer&#039;s IP which modify data ,to cdc table as new field example:changed_byhost,changed_byip.is there any way for 
add this field to cdc tables?]]></description>
		<content:encoded><![CDATA[<p>hi all.<br />
we use cdc tables for store modified data in database and we can see those easily,but now we want to add host name<br />
and computer&#8217;s IP which modify data ,to cdc table as new field example:changed_byhost,changed_byip.is there any way for<br />
add this field to cdc tables?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ninad Kulkarni</title>
		<link>http://blog.sqlauthority.com/2009/12/25/sql-server-cdc-and-truncate-cannot-truncate-table-because-it-is-published-for-replication-or-enabled-for-change-data-capture/#comment-60248</link>
		<dc:creator><![CDATA[Ninad Kulkarni]]></dc:creator>
		<pubDate>Wed, 27 Jan 2010 01:08:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7625#comment-60248</guid>
		<description><![CDATA[Dog there is one more flaw in CDC. If you try to update primary key of the source table which is being cdc-ed then it gets published as delete and insert and not just the update in to that cdc table. I&#039;ve contacted Microsoft about this and they said it&#039;s by &quot;DESIGN&quot;!]]></description>
		<content:encoded><![CDATA[<p>Dog there is one more flaw in CDC. If you try to update primary key of the source table which is being cdc-ed then it gets published as delete and insert and not just the update in to that cdc table. I&#8217;ve contacted Microsoft about this and they said it&#8217;s by &#8220;DESIGN&#8221;!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Saurabh</title>
		<link>http://blog.sqlauthority.com/2009/12/25/sql-server-cdc-and-truncate-cannot-truncate-table-because-it-is-published-for-replication-or-enabled-for-change-data-capture/#comment-59020</link>
		<dc:creator><![CDATA[Saurabh]]></dc:creator>
		<pubDate>Sun, 27 Dec 2009 05:38:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7625#comment-59020</guid>
		<description><![CDATA[Its really good concept]]></description>
		<content:encoded><![CDATA[<p>Its really good concept</p>
]]></content:encoded>
	</item>
</channel>
</rss>
