|
Home > Archive > MS SQL Server Replication > September 2005 > Merge Replication and Begin and commit tran
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Merge Replication and Begin and commit tran
|
|
|
| We have replication setup concurrently. In this scenario does the
transactions will get commited only after replication? What happens if the
replication fails due to one of these errors
a) Invalid subscription
b) Waiting for a connection
The reason for this question, quite often when we get replication error
message, we notice that some of the committed transactions are getting rolled
back . These commited tranactions tables the primary key column datatype is
identity
Need inputs from forum on this.
| |
| Hilary Cotter 2005-09-16, 9:23 am |
| Transactions are always committed on the publisher or subscriber. They can
be rolled back after synchronization. If you have an invalid subscription
there is no synchronization. If you have a waiting for connection error
message - no synchronization takes place.
I hope this answers your question.
--
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
"SouRa" <SouRa@discussions.microsoft.com> wrote in message
news:CDF0A41B-9C89-45D1-9090- B267351892C4@microso
ft.com...
> We have replication setup concurrently. In this scenario does the
> transactions will get commited only after replication? What happens if the
> replication fails due to one of these errors
>
> a) Invalid subscription
> b) Waiting for a connection
>
> The reason for this question, quite often when we get replication error
> message, we notice that some of the committed transactions are getting
rolled
> back . These commited tranactions tables the primary key column datatype
is
> identity
>
> Need inputs from forum on this.
|
|
|
|
|