Re: Identity Column - transactional replication with immediate update

From: Hilary Cotter (hilary.cotter_at_gmail.com)
Date: 09/20/04 

Date: Mon, 20 Sep 2004 13:11:46 -0400

I think this is by design. This condition should clear when the distribution
agent runs. To get around it set the polling interval to something small (ie
1 s) and run your distribution agent continuously. 

-- 
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Thomas" <Thomas.Eriksson@intress.se> wrote in message
news:evvkICznEHA.1608@TK2MSFTNGP15.phx.gbl...
> Hi,
>
> We have a problem that we can't find a solution to ... yet ...
> I hope someone can help us out.
>
> I will try to discribe the problem below.
>
> 1. We publish a publication with articles to the subscriber(s) in
immediate
> replication mode.
> 2. The we make an insert at the subscriber side.
> 3. The inserted record pops up at the publisher (and other subscribers)
> almost immediate as it
> should.
> 4. But the msrepl_tran_version column differs between the publisher
> and the subscriber!!
>     Therefore it is not allowed to update the newly inserted record at the
> subscriber site. We get the error message
> "Rows do not match between Publisher and Subscriber. Run the Distribution
> Agent to refresh rows at the Subscriber." The Agent IS running.
> 5. The msrepl_tran_version remains different UNTIL you make an update at
the
> publisher site (or at another subscriber that have the same value in
> msrepl_tran_version as the publisher)
> 6. After an update at the publisher it is now perfectly allowed to make
> updates to the
> record at the same subscriber site that made the insert.
> This applies only to records that are inserted from the specific
subscriber,
> all other records works just fine....
>
> An insert into a table without Identity collumn works fine ....
> The Identity property is set to 'Yes'.
>
> I hope that someone have a clue of what we are missing here ...
>
> Best Regards
> Thomas
>
>

Relevant Pages

  • Re: Server SQLTEST1 is not prepared to run the offloaded agent
    ... By default the distributor will be on the server which you created it on, ... If you are using a pull subscription you will have to enable the subscriber ... Your publisher by default will use the distribution database it ...
    (microsoft.public.sqlserver.replication)
  • Re: undocumented agent profile parameters
    ... dedicated when you the merge replication related procs and commands are run ... I would venture to say that the performance of the merge agent is more ... When I hear the words performance and blocking on the publisher with ... Is "source" a publisher or subscriber? ...
    (microsoft.public.sqlserver.replication)
  • Re: Newbie question: "No replicated transactions are available"
    ... The log reader agent will read your transaction log and construct commands ... which it writes to the distribution database. ... reads these commands and applies them on the subscriber. ... The snapshot agent will generate scripts and data files which will be ...
    (microsoft.public.sqlserver.replication)
  • RE: Merger Replication - SQL2000
    ... you cannot use SQL2000 subscriber to merge when publisher is SQL2005. ... snapshot, and use nosync option when creating subscription, the merge agent ... we were unable to get merger replication to work ...
    (microsoft.public.sqlserver.replication)
  • Re: SqlExpress Merge Agent slow Profiles & one way Rep
    ... I have a publishing subscriber which publishes to SQLExpress. ... You are saying that if I set "slow profile" on the publisher SQLExpress will ... Surely the profiles exist where the Agent runs, which for a Merge agent is ...
    (microsoft.public.sqlserver.replication)