What it seems you are looking for is bi-directional replication.
So ServerX publishes TableA to Server Y which also publishes Table A to
Server X.
you can use Merge Replication, or bi-directional transactional replication
for this. You can also use immediate updating with Transactional replication
ONLY if your servers are always up and the link is always reliable, and the
majority of the transactions originate at the publisher. If not consider
Queued updating if you can't guarantee the stability of the link or if your
Publisher goes off line and the majority of the transactions originate at
the Publisher.
--
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html [quoted text, click to view] "Afaq" <Afaq@discussions.microsoft.com> wrote in message
news:900D73DA-FE60-4C98-8829-C7834B5641B3@microsoft.com...
> Hi,
>
> Please consider the following scenario
>
> Table A is an article in a publication on Server X. Server Y is a
subscriber
> to this pubication. Server Y also can be a publisher for Table A and
Server X
> can be a subscriber for the same. WHen i have a subscription on table A
from
> server Y i cant have a publication for the same table from Server Y.
> How do i achieve the same? I need Table A to be a part of different
> publications from different servers as they are in different time zones
and
> they will publish the data on different times. And we want each of the
> servers to publish the data for the same table at different times.
> I hope the issue is properly conveyed. Forgive me for asking this question
> as i am a newbie in replication.
>
> Thanks in advance
> --
> Afaq Choonawala