will transnational replication made changes to the source tables?
hi all:
here situation: want replication few big tables taba, b, c server 1 server 2. we thinking using transactional replication have few concerns schema changes it's gonna make on articles.
my questions:
1. transactional replication add new tracking columns source tables taba,b,c? we can't tolerate production schema changes.
thanks
hui
--currently using reporting service 2000; visual studio .net 2003; visual source safe ssis 2008 ssas 2008, svn --
yes if have configured transactional replication updatable subscriptions.
why replication add column replicated tables; removed if table isn't published?to track changes, merge replication , transactional replication queued updating subscriptions must able uniquely identify every row in every published table. accomplish this:
-
merge replication adds column rowguid every table, unless table has column of data type uniqueidentifier rowguidcol property set (in case column used). if table dropped publication, rowguid column removed; if existing column used tracking, column not removed.
-
if transactional publication supports queued updating subscriptions, replication adds column msrepl_tran_version every table. if table dropped publication, msrepl_tran_version column not removed.
-
a filter must not include rowguidcol used replication identify rows. default column added @ time set merge replication , named rowguid.
source :https://msdn.microsoft.com/en-us/library/ms151740.aspx
hope helps
thanks
SQL Server > SQL Server Replication
Comments
Post a Comment