﻿<?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 7,2000 / Replication  / Replication: / 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>Thu, 23 May 2013 19:46:11 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Replication:</title><link>http://www.sqlservercentral.com/Forums/Topic894572-7-1.aspx</link><description>because the replication agent needs a way to unqiuely identify the rows,  otherwise how would the replication agent know what row to update on the subscribers?also it is expected that in any relational database that all tables will have a primary key, otherwise you really need to look at your design because you are going to run into issues at some stage, whether you use replication or not.</description><pubDate>Thu, 01 Apr 2010 05:03:38 GMT</pubDate><dc:creator>steveb. </dc:creator></item><item><title>Replication:</title><link>http://www.sqlservercentral.com/Forums/Topic894572-7-1.aspx</link><description>why transactional replication works only on primary key tables.Why we can't include any non primary key  table as an article in replication</description><pubDate>Thu, 01 Apr 2010 04:25:45 GMT</pubDate><dc:creator>Alone</dc:creator></item></channel></rss>