Re: ABNORMAL Transactional Replication behaviour

Tech-Archive recommends: Speed Up your PC by fixing your registry

Thanks Hilary for the advice, but sp_browsereplcmds reveals only that the last command was the one for the last record send from the subscriber to the published database(no cmds for the records in the subscriber and not replicated to the publisher). Then i tried to run sp_repltrans on my publication db but it returns me no results... All the agents continue "working" without any error, but no more records are replicated (neither from pubisher to subscriber or vice-versa). Wherelse can i search for the transactions failed? I mean...

Any other idea? The main thing that upsets me is that i'm not able to see what's going wrong!! I'll try changing some configurations.... I'm using a push subscription... is it better to use a pull one?
I really need some help...

thanks....


Hilary Cotter ha scritto:
what does ? Run this in the distribution database to see if commands are pooling there.

If they aren't run sp_repltrans in your publication database.



.

Relevant Pages

  • Re: PULL subscriber problem SQL Server 2000
    ... It says it can't find the server Marius or the share repl. ... Go to the publisher and issue the same command. ... >> can you connect to your subscriber using QA with the sa account, ...
    (microsoft.public.sqlserver.replication)
  • Re: Unable to configure pull subscription
    ... can you also tell use what happens when you run this command in isqlw on ... > am using MSDE on both subscriber and a publisher. ... > Error message here ...
    (microsoft.public.sqlserver.replication)
  • Re: Fwd: [SLE] Warning about your e-mail account.
    ... unsigned mail are extremely easy to forge ... The address of the subscriber is in the envelope of the mail. ... in the "MAIL FROM" command. ...
    (SuSE)
  • RE: how to check which command waiting for transfering to subscrib
    ... The dataon the subscriber is treated as read only, ... I checked replication in replication monitor, and there 700 command waiting ... for transfering to subscriber in distributor, ...
    (microsoft.public.sqlserver.replication)
  • Row not found at subscriber
    ... The row was not found at the Subscriber when applying the replicated ... We dropped the old publication and created a new publication from scratch. ... applying the replicated command. ... replicate as updates instead of inserts/deletes. ...
    (microsoft.public.sqlserver.replication)