Multiple Updatable Publication on the same table!!

Hi,

I have created a publication for sql server 2005 Mobile Edition subscriber,

I need to add another Publication/merge replication on the same tables,

Scenario:

-Server A and mobile devices (publication for sql server 2005 Mobile Edition subscriber)

-The same Server A send data "1 way direction" to Server B by merge replication publication.

NB: My Tables are updatble in both publications.

Any idea?

Thanks,

Tarek Ghazali

SQL Server MVP

Are you getting an error that's preventing this from happening?

Multiple Updatable Publication on the same table!!

Hi,

I have created a publication for sql server 2005 Mobile Edition subscriber,

I need to add another Publication/merge replication on the same tables,

Scenario:

-Server A and mobile devices (publication for sql server 2005 Mobile Edition subscriber)

-The same Server A send data "1 way direction" to Server B by merge replication publication.

NB: My Tables are updatble in both publications.

Any idea?

Thanks,

Tarek Ghazali

SQL Server MVP

Are you getting an error that's preventing this from happening?

Multiple Subscribers

One Publication with multiple-server subscribers (same articles).
1. Do the subscribers use the same snapshot or you have to reinitialize for
each?
2. Can the replication be scheduled at the same time without possible
latency on the publisher?
Morphius,
it depends on the transaction retention period and if anonymous subscribers
are set up or not. If you don't have anonymous subscribers, the cleanup
agent will remove the snapshot files once the last subscriber has
initialized, so you'll need to create a new snapshot. With anonymous
subscribers, the snapshot will stick around until the retention period is
reached, as will the changes made to the articles.
Not too sure what the second question means. When you talk about replication
being scheduled, do you mean a snapshot or distribution/merge
synchronization. At the same time as which process?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Paul,
The second question means synchronization of snapshots to subscribers. I
just want to make sure that the same articles are published to different
servers(subscribers). Thank you.
"Paul Ibison" wrote:

> Morphius,
> it depends on the transaction retention period and if anonymous subscribers
> are set up or not. If you don't have anonymous subscribers, the cleanup
> agent will remove the snapshot files once the last subscriber has
> initialized, so you'll need to create a new snapshot. With anonymous
> subscribers, the snapshot will stick around until the retention period is
> reached, as will the changes made to the articles.
> Not too sure what the second question means. When you talk about replication
> being scheduled, do you mean a snapshot or distribution/merge
> synchronization. At the same time as which process?
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
>
|||Yes - the same articles can be sent to multiple subscribers. As far as I
know you can't guarantee that this is completely synchronized though - the
distribution agents won't necessarily all finish at the same time, even if
you have multiple processors there's no way of guaranteeing this.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .

Multiple Subscriber / Publisher scenario

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
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
"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