﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / SQL Server 2008 / SQL Server 2008 - General  / rowversion vs Change Tracking / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Sat, 18 May 2013 14:32:45 GMT</lastBuildDate><ttl>20</ttl><item><title>rowversion vs Change Tracking</title><link>http://www.sqlservercentral.com/Forums/Topic1347458-391-1.aspx</link><description>I'm trying to determine whether I should use the rowversion column to find data changes for an ETL process that will push updates to a cube. According to Erland Sommarskog, in the post linked to below, "if there are plenty of concurrent updates, it can become very difficult to avoid that you miss changes" using rowversion. Unfortunately I can't find more information about that and while I trust Erland, it would be easier to use rowversion if we could.http://social.msdn.microsoft.com/Forums/en/transactsql/thread/7f1cea96-7cf4-4feb-97f4-c15095adf449</description><pubDate>Mon, 20 Aug 2012 13:55:02 GMT</pubDate><dc:creator>AlBran LVP</dc:creator></item></channel></rss>