Showing posts with label merge. Show all posts
Showing posts with label merge. Show all posts

Friday, March 23, 2012

Question about Merge Replication

How is it possible to use single database as a pull subscriber to one Merge Publication and as a Merge Publisher to few push subcriptions?! Actually i have a 3 tiers heirachy in which i need to update data in all directions. For this i need to use Merge replication at all layers but the problem is at the middle layer ( intermidiate Database ).

Please help me.

Regards,

Sorry, it's not clear what you're asking. Are you asking how merge handles changes at differenet nodes, or are you asking about internal details? And I'm not clear what you mean by "middle layer", or intermediate database.

I'm not sure what a three tier hierarchy in your scenario is, but you can have one machine be a publisher/distributor, and the other two machines be subscribers. Changes made at the publisher will flow down to the two subscribers. Changes made at the subscribers will flow up to the publisher, and if necessary, back down to the other subscriber.

|||Sorry if the question was not clear. In Simple words i need to implement a "Publishing-Subscriber Model". Means i need my subscriber be publisher for another subscriber.

Regards,|||What is the reason for needing to republish? You should only want to do this if you need to scale out. Is this what you're trying to accomplish?

Question about Merge Agent

Does anyone know of a reasource that will describe exactly what happens during merge replication. I particular, I would like to know what is happening when the merge agent history says "Downloaded xxx data changes". Where is it downloading it to?
Downloaded refers to Publisher->Subscriber changes, while uploaded is the converse (information stored in dbo.MSmerge_history). To get further information on this and related topics, BOL is currently the best resource. Have a look at 'merge replication, o
verview' as a good page to navigate from.
HTH,
Paul Ibison
sql

Friday, March 9, 2012

question about conflicts

hi all,
I am using merge replication with push subscription.i am getting conflicts
in some tables.i am not resolving any conflicts.so the system can resolve or
those conflicts can be cleaned.please suggest how to resolve conflicts.
with the help of rowguid can i retrive the entire record which came in
conflict
in which table it is available
please suggest information to review the conflicts
thanks
reddy
right click on your publication and select view conflicts. When the conflict
viewer comes up you can resolve the conflicts using the Keep Wining Change,
Show or Edit the conflicts, or Resolve with this data choices.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"reddy" <reddy@.discussions.microsoft.com> wrote in message
news:EC863DF6-3E55-4F62-8990-0825D579E710@.microsoft.com...
> hi all,
> I am using merge replication with push subscription.i am getting conflicts
> in some tables.i am not resolving any conflicts.so the system can resolve
or
> those conflicts can be cleaned.please suggest how to resolve conflicts.
> with the help of rowguid can i retrive the entire record which came in
> conflict
> in which table it is available
> please suggest information to review the conflicts
> thanks
> reddy
>
|||Hillary,
I am able to see the conflicts through the conflict viewer but Unable to
track all columns part of the conflict.my table structure
contains userid and createdate columns.if any user from publisher side or
subscriber side is trying to update the row then we will capture that userid
and date for reference.
Whenever a conflict occurs we are not able to view the userid
information part of the conflicts. This is required for us to identify the
source of the conflict
We want to rule out the following assumptions
a) conflict can occur within subscriber or publisher when an update happens .
In our merge replication process , conflict only occurs at update. NO
conflicts during inserts.
please help.now the database is in production i am unable to rectify this
problem.
awaiting for your response
your help is appreciated
regards
reddy
"Hilary Cotter" wrote:

> right click on your publication and select view conflicts. When the conflict
> viewer comes up you can resolve the conflicts using the Keep Wining Change,
> Show or Edit the conflicts, or Resolve with this data choices.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "reddy" <reddy@.discussions.microsoft.com> wrote in message
> news:EC863DF6-3E55-4F62-8990-0825D579E710@.microsoft.com...
> or
>
>