Replication Report

Hi,
Is there anyway to provide weekly status report of the replication. Like --
1. Which tables are replicated.
2. When replication is not possible with reason.
Thanks in advance.
This shouldn't be too difficult to produce. Sysarticles and sysmergearticles
on the publisher will give the first part. The distribution database
(MSrepl_errors, MSdistribution_history, MSsnapshot_history etc) will give
the latter. Reporting Services for the report then you're done.
HTH
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||You'll probably want to bump your history retention up to something more
than a week - by default it hangs around for 3 days. To do this, right click
on Replication Monitor, select Distributor Properties, and then click on the
properties button. Change History Retention here.
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
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:etnRVW5gFHA.2372@.TK2MSFTNGP14.phx.gbl...
> This shouldn't be too difficult to produce. Sysarticles and
sysmergearticles
> on the publisher will give the first part. The distribution database
> (MSrepl_errors, MSdistribution_history, MSsnapshot_history etc) will give
> the latter. Reporting Services for the report then you're done.
> HTH
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
sql

Replication PK/FK conflict

We have established a Report server (subscriber) for our
OLTP production database (publisher). Transaction
replication is running between the two databases.
An UPDATE on the OLTP database is triggering a
DELETE/INSERT on the Report database. This DELETE is
causing a FK conflict and results in replication errors.
It appears that if an UPDATE is done on an index key, this
causes a DELETE/INSERT instead of an UPDATE. Is there any
way to handle this without dropping the FKs on the Report
(subscriber) database in replication?
Thanks
Jay,
this is a known issue. There is a solution though:
http://support.microsoft.com/default...NoWebContent=1
hth,
Paul