I can send you the text of the update if you like." First, here's a knowledge base article to read.Second, here's your architecture as I understand it: SQL1 is the publisher SQL2 is the distributor and is a subscriber SQL3 is a subscriber All replication is transactional replication, and it's all one-way (transactions are going from SQL1 to SQL2 and SQL3).However, with SQL Server 7 updateable copies of data can be replicated.This means that copies of the same data can be available on two different servers and should the data on one server be updated then that change will be replicated to (i.e. Back to Top An understanding of SQL Server Replication terminology is useful, but not essential, for setting up and maintaining a replicated system.The following is a list of the terms used with SQL Server Replication.A distribution database tracks the changes (to publications) that need to be replicated (from publishers).Partition the data if you can, otherwise just make sure you send your updates to the publisher and let them filter down. That's a whole separate article, though.rocketscientist. Error: In Transactional Replication with immediate updating subscription Update to a row in subscriber which is already updated in publisher is not possible.
Refresh rows at Subscriber./weborder.asp, line 134The line in question is the rs.execute statement which sends an update through to the database.Customers from different countries open the website and then redirected to the website for their respective country.The website is redirecting to the application server which connects database on backend locally, but all country database needs to be in sync.With immediate transactional consistency each site must simultaneously commit the change.Immediate Transactional Consistency therefore has a performance impact, because of which it is unlikely to be suitable for high performance databases or where replicating over a slow LAN or a WAN.The error you're getting occurs when the updates to the publication are being applied at the subscriber simultaneously with an update from your web client. Since you're working with immediate updating subscriptions, select data from SQL2/SQL3 and update only to SQL1. That way your replication isn't stepping on your updates.2. If your architecture is the way it is because you have some data that is largely static on SQL1 and is published to 2 and 3, and the updates on 2 and 3 are to a different set of tables, then partition the data into a database that gets published out for the static tables and a database that is updated for the ones that change.