Conflits with transactional replication

hello,
i need your help.
i have a transactional plublisher database, with updatable subscribers, and
used a queued update.
i have a lot of problems, first i need to use triggers in both siders, to
update 2 replicates tables, and now i have many conflicts, because they
update both records.
my first question is, i need to change my transactional replication, to
remove tow tables for replication, if i remove that, the transactional
replication reinitialize?
second question is, i need that a replicated table use triggers in both side
(publisher and subscriber), but not "not for replication" can i do this?
thanks,
manuel ralha
I think the majority of your problems can be solved by using the Not For
Replication attribute on your triggers.
Dropping articles will require a new snapshot to be generated or a
reinitailzation.
If you really need the triggers to fire on both side and to be fired by a
replication process you must make sure they do not modify the same data, or
if so, do an existence check to see if they really need to update/insert/ or
delete rows. I don't know what your trigger logic is, but to avoid the
conflicts it sounds like you need to re-write your trigger.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"manuel ralha" <manuelralha@.discussions.microsoft.com> wrote in message
news:723FD107-DE30-4755-AC0F-6181E352F9CC@.microsoft.com...
> hello,
> i need your help.
> i have a transactional plublisher database, with updatable subscribers,
> and
> used a queued update.
> i have a lot of problems, first i need to use triggers in both siders, to
> update 2 replicates tables, and now i have many conflicts, because they
> update both records.
> my first question is, i need to change my transactional replication, to
> remove tow tables for replication, if i remove that, the transactional
> replication reinitialize?
> second question is, i need that a replicated table use triggers in both
> side
> (publisher and subscriber), but not "not for replication" can i do this?
> thanks,
> manuel ralha

Conflict resolution for Transactional Replication with Updating Subscribers

Hi.
I'm trying to establish whether Transactional Replication with
Updating Subscribers meets my requirements. I have chosen to use
"publisher wins" for the conflict resolution. (I'm using SqlServer
2005 Developer Edition on Win XP SP2 on both machines)
When I cause a conflict to occur by making an update to rows with the
same PK on both servers, the publisher indicates that there has been a
conflict, and that it chose the publisher as the winner. However, the
losing transaction on the subscriber does not seem to be rolled back
like this article says it should: http://msdn2.microsoft.com/en-us/library/ms151177.aspx.
I'm then left in the state where the two tables are out of sync.
Any ideas anyone?
Cheers!
Some extra info...
I forgot to mention earlier that I'm using a push subscription.
I've found that if I choose 'subscriber-wins' instead, then it seems
to work OK, but unfortunately this is not what I require.
'Normal' changes to data on both servers are correctly replicated to
the other server. It's just publisher-wins conflict resolution that
doesn't seem to work. The conflict is detected, but the publisher's
data is not applied to the subscriber (i.e. the subscriber change is
not rolled back).. Any further changes to that row fail to go through
following the conflict.
Any comments appreciated,
Rich.
On 23 Feb, 08:22, ricisb...@.yahoo.co.uk wrote:
> Hi.
> I'm trying to establish whether Transactional Replication with
> Updating Subscribers meets my requirements. I have chosen to use
> "publisher wins" for the conflict resolution. (I'm using SqlServer
> 2005 Developer Edition on Win XP SP2 on both machines)
> When I cause a conflict to occur by making an update to rows with the
> same PK on both servers, the publisher indicates that there has been a
> conflict, and that it chose the publisher as the winner. However, the
> losing transaction on the subscriber does not seem to be rolled back
> like this article says it should:http://msdn2.microsoft.com/en-us/library/ms151177.aspx.
> I'm then left in the state where the two tables are out of sync.
> Any ideas anyone?
> Cheers!

Conflict Management

Hello:
If merge replication uses anonymous pull subscriptions and
the subscribers have no sql server tools installed, how can the
subscribers resolve conflicts? (Can we provide a program interface to
help do this?)
Does replication(merge) preserve transactional integrity
while doing updates to the publisher, if there is a conflict. (That
is, if a updated table, that was updated in a transaction on a
replicated database, conflicts with another replicated database, since
this information waits in conflict tables till resolved, will the
whole transaction wait or will the remaining tables proceed to update
themselves?)
Thanks for the help,
Hananiel
The conflict viewer is one possibility. I believe this ships with Office
2003. The SQL 2000 Resource kit has a chapter devoted to the Conflict
Resolver object. You might want to build your own conflict resolver app.
"Hananiel" <hananiel@.yahoo.com> wrote in message
news:e338e321.0410110813.771d55a8@.posting.google.c om...
> Hello:
> If merge replication uses anonymous pull subscriptions and
> the subscribers have no sql server tools installed, how can the
> subscribers resolve conflicts? (Can we provide a program interface to
> help do this?)
> Does replication(merge) preserve transactional integrity
> while doing updates to the publisher, if there is a conflict. (That
> is, if a updated table, that was updated in a transaction on a
> replicated database, conflicts with another replicated database, since
> this information waits in conflict tables till resolved, will the
> whole transaction wait or will the remaining tables proceed to update
> themselves?)
> Thanks for the help,
> Hananiel

Configuring new Subscriber. Publisher can't connect to Subscriber

Hi,
Both the publisher and subscriber are SQL 2005 SP2. I am trying to set up a
new subscriber to a push replication. I have other subscribers that are
working fine. When I try to add a new subscriber I am specifying the
computers name as the 'Server Name'. When the wizzard attempts to connect I
receive an error specifying that 'Cannot connect to XXXXX'. 'Timout expired.
The timeout period elapsed prior to completion of hte operation or the
server is not responding. (Microsoft SQL Server). Is these something that I
need configured on the subscriber machine? I'm sure I am missing something
obvious.
Thanks for your help,
Terry
its hard to say what is the problem here. Set the login timeout to something
large, perhaps 300. Enable logging to see if you can see where it is getting
stuck.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Terry Wahl" <TerryWahl@.discussions.microsoft.com> wrote in message
news:78D0CB4F-5EFA-4D15-B13B-8F54F8D1BF2C@.microsoft.com...
> Hi,
> Both the publisher and subscriber are SQL 2005 SP2. I am trying to set up
> a
> new subscriber to a push replication. I have other subscribers that are
> working fine. When I try to add a new subscriber I am specifying the
> computers name as the 'Server Name'. When the wizzard attempts to connect
> I
> receive an error specifying that 'Cannot connect to XXXXX'. 'Timout
> expired.
> The timeout period elapsed prior to completion of hte operation or the
> server is not responding. (Microsoft SQL Server). Is these something
> that I
> need configured on the subscriber machine? I'm sure I am missing
> something
> obvious.
> Thanks for your help,
> Terry
|||Hi Hilary,
Thanks for the reply. It turns out that the firewall was the issue. Here
is the document that I used to configure the firewall:
http://msdn2.microsoft.com/en-us/library/ms175043(SQL.90).aspx
Thanks again,
Terry
"Hilary Cotter" wrote:

> its hard to say what is the problem here. Set the login timeout to something
> large, perhaps 300. Enable logging to see if you can see where it is getting
> stuck.
> --
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Terry Wahl" <TerryWahl@.discussions.microsoft.com> wrote in message
> news:78D0CB4F-5EFA-4D15-B13B-8F54F8D1BF2C@.microsoft.com...
>
>