Replication Question

Dear All,
After marked re-initialize an existing publication, a new snapshot has been
generated and applied to the subsciber, after that, there is an error on
Distributor agent saying that can't apply command as duplicate key error. I
have checked those insert commands and those records are already exists on
subsciber as new snapshot has been applied.
What I can do to resolve the problem? Do Distributor agent is smart enought
to ignore those old not yet replicated transactions which is older than my
latest snapshot being applied? What is the correct action sequence for
re-initialization?
Yours sincerely,
Henry
Henry,
see if this applies:
http://support.microsoft.com/default...b;en-us;813494
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Henry,
also, have a look at the post 'Subscription Choking' from yesterday, as
there might need to be an additional step if the Hotfix is applied:
http://groups-beta.google.com/group/...8?dmode=source
Rgds,
Paul Ibison
sql

Replication Latency

Hi:
Latency is very high in replication monitor even though I don't see any
commands to be applied in sp_browsereplcmds. Do you know from where it gets
the latency number from in distribution database because it is misleading?
Thanks
IIRC it gets it from the table MSreplication_monitordata in the distribution
database.
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
"Sal" <Sal@.discussions.microsoft.com> wrote in message
news:ACB19921-E431-4DDE-A7EB-F2D1935E84D3@.microsoft.com...
> Hi:
> Latency is very high in replication monitor even though I don't see any
> commands to be applied in sp_browsereplcmds. Do you know from where it
> gets
> the latency number from in distribution database because it is misleading?
> Thanks
|||I can't find this table "MSreplication_monitordata" in distribution database.
"Hilary Cotter" wrote:

> IIRC it gets it from the table MSreplication_monitordata in the distribution
> database.
> --
> 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
>
> "Sal" <Sal@.discussions.microsoft.com> wrote in message
> news:ACB19921-E431-4DDE-A7EB-F2D1935E84D3@.microsoft.com...
>
>
|||You use the term replication monitor which is a tool in SQL 2005. What
version of SQL Server are you running?
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
"Sal" <Sal@.discussions.microsoft.com> wrote in message
news:565FB679-582F-4933-9E9D-F9CE558EACEA@.microsoft.com...[vbcol=seagreen]
>I can't find this table "MSreplication_monitordata" in distribution
>database.
> "Hilary Cotter" wrote:
|||I am using sql server 2000. Please let me know
"Hilary Cotter" wrote:

> You use the term replication monitor which is a tool in SQL 2005. What
> version of SQL Server are you running?
> --
> 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
>
> "Sal" <Sal@.discussions.microsoft.com> wrote in message
> news:565FB679-582F-4933-9E9D-F9CE558EACEA@.microsoft.com...
>
>
|||Don't forget to take into account the polling intervals of your
logreader and distribution agents. Even though theses agents seem to
run continuously they in fact do not. Check out BOL for the default
intervals. I think they are around 5secs. One way of reducing latency
is by reducing this refresh interval. Be careful though you need to
strike a balance between low latency and agent thrashing away trying
to get data all the time.
Regards,
Jim Katsos
http://jims-spanakopita.blogspot.com/

Replication issues with failed logins

I just applied instcat.sql to my SQL Srvr 2k sp4. At first it broke my replication with some cursor errors. Applying the latest instcat.sql fixed the problem, however one of the distribution agents would not start (i'm not sure if instcat had anything to do with it) giving me a "Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. The process could not connect to distributor 'DistributorName'. The step failed." error.

Any suggestions would be greatly appreciated!

Thanks!

For those who experience similar problems: I simply ran distribution agent at Distributor. That fixed the issue.