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 on SQL 2000

I have a question regarding functionality with SQL 2000.
In 2005, there are several sys.dm tables that provide information regarding
the database/OS/Hardware ect... I can use these tables to check the status of
replication amoungst other things.
I know SQL 2000 does not have these tables, but was wondering if there was a
way to trap some of this information. More specifically, the status of the
distribution agent. The reason for this is that I have a 2005 box that
suscribes to a 2000 box and I can't locate any information in the sys.dm
tables regarding this subscription.
try sp_MSenum_replication_agents @.type = 3, @.exclude_anonymous = 0
If you want specific agents query
distribution.dbo.msdistribution_agent_history
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
"Big Ern" <BigErn@.discussions.microsoft.com> wrote in message
news:3C81CF85-86D6-4115-9A63-9B96B5A6A432@.microsoft.com...
>I have a question regarding functionality with SQL 2000.
> In 2005, there are several sys.dm tables that provide information
> regarding
> the database/OS/Hardware ect... I can use these tables to check the status
> of
> replication amoungst other things.
> I know SQL 2000 does not have these tables, but was wondering if there was
> a
> way to trap some of this information. More specifically, the status of the
> distribution agent. The reason for this is that I have a 2005 box that
> suscribes to a 2000 box and I can't locate any information in the sys.dm
> tables regarding this subscription.

Replication Monitor SqlServerCE

I have developed a smart device application using SqlServerCE that replicates data to the backend server. I need to provide to the user a status of this replication process. I read about the "MergeSubscriberMonitor" in SQL Server but can't find it in SqlServerCe. Is this possible? Can someone please point me in the right direction?You need to wait for synchronisation to finish and then you can query to MergeReplication object to report on the data transferred.

If you were using SQLMobile (the CE version for SQL 2005), there is messaging available that will give you progress updates.|||I'm not sure I understand what your comment "messaging" is referring to. Do you have or can point me to some sample code that uses messaging? I am using SQL CE on the mobile device.|||Sorry, by messaging I mean events that you can catch within code and then react to. With SQL CE I don't believe this is happening. You can only query the replication object at the completion of the synchronisation process in order to determine what the outcome was (data sent and received)|||Thanks for your response. I did try asynchronous replication and it is working well so far. I need to implement some additional error trapping but I think I have 95% of what I need. It allows me to get a "percent of completion" during the sync process. I can then display this on the screen to my users. The database is VERY large and was taking forever to sync. I really needed some type of progress bar to show the user. Without that status update, it appeared the unit was locked up. Thanks anyway for your reponse.|||Hi,

I am also trying to get a status update on each article during the web synchronization process. Can you please update me on how to monitor the percent complete progress for the replication.

Thanks in advance.

Apurva

Replication Monitor SqlServerCE

I have developed a smart device application using SqlServerCE that replicates data to the backend server. I need to provide to the user a status of this replication process. I read about the "MergeSubscriberMonitor" in SQL Server but can't find it in SqlServerCe. Is this possible? Can someone please point me in the right direction?You need to wait for synchronisation to finish and then you can query to MergeReplication object to report on the data transferred.

If you were using SQLMobile (the CE version for SQL 2005), there is messaging available that will give you progress updates.|||I'm not sure I understand what your comment "messaging" is referring to. Do you have or can point me to some sample code that uses messaging? I am using SQL CE on the mobile device.|||Sorry, by messaging I mean events that you can catch within code and then react to. With SQL CE I don't believe this is happening. You can only query the replication object at the completion of the synchronisation process in order to determine what the outcome was (data sent and received)|||Thanks for your response. I did try asynchronous replication and it is working well so far. I need to implement some additional error trapping but I think I have 95% of what I need. It allows me to get a "percent of completion" during the sync process. I can then display this on the screen to my users. The database is VERY large and was taking forever to sync. I really needed some type of progress bar to show the user. Without that status update, it appeared the unit was locked up. Thanks anyway for your reponse.|||Hi,

I am also trying to get a status update on each article during the web synchronization process. Can you please update me on how to monitor the percent complete progress for the replication.

Thanks in advance.

Apurva

replication history not being logged

I recently discovered the mslogreader_history and msdistribution_history
tables (thanks Hilary) and like the info they provide. However, I switched
from the default Distribution and Log Reader Profiles and assigned my own.
After I made the switch info isn't making it into thes tables? How do I
change this?
SQL2K SP3
TIA, ChrisR
what is your HistoryVerboseLevel? It should be 1 or 2, and not 0.
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"ChrisR" <bla@.noemail.com> wrote in message
news:OcRFqgs3EHA.2404@.TK2MSFTNGP14.phx.gbl...
>I recently discovered the mslogreader_history and msdistribution_history
> tables (thanks Hilary) and like the info they provide. However, I switched
> from the default Distribution and Log Reader Profiles and assigned my own.
> After I made the switch info isn't making it into thes tables? How do I
> change this?
> --
> SQL2K SP3
> TIA, ChrisR
>
|||Dist = 1. LogReader = 2.What is this anyways?
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:ualE1ms3EHA.3388@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> what is your HistoryVerboseLevel? It should be 1 or 2, and not 0.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> Now available for purchase at:
> http://www.nwsu.com/0974973602.html
> "ChrisR" <bla@.noemail.com> wrote in message
> news:OcRFqgs3EHA.2404@.TK2MSFTNGP14.phx.gbl...
switched[vbcol=seagreen]
own.
>
|||0 means no history is logged and you should be running with 0 for
performance reasons. 1 means minimal logging, 2 means more logging and 3
means verbose. Verbose should only be used for debugging because it degrades
overall performance. 1 will only display the last historical record in the
agent dialog. For instance when you drill down on the agent, it will show a
history of the activity - connecting to publisher, connecting to subscriber,
23 transactions and 23 commands replicated. You will be unable to drill
down any further. Setting the history to 2 will allow you to drill down and
see more historical information on the messages, ie a list of transactions
and commands delivered in the past.
However - I am bewildered by why you are not seeing any historical
information. With the HistoryVerboseLevels you have you should be seeing
information. Can you perhaps bounce these agents and see if the bounce will
fix the problem? If you make changes to the profile or the agent parameters
they will only be effective when the agent is stopped and restarted.
There is also a condition where the buffers are depleted/exhausted that the
agents use to connect to SQL Server with and they hang in a perpetual state
of connecting/initializing. In my lifetime, I have only seen this once, and
on this newsgroup I think I have seen it a couple of times - so it is
relatively rare. You will have to reboot your machine to clear this
condition.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"ChrisR" <bla@.noemail.com> wrote in message
news:%23wu703s3EHA.2336@.TK2MSFTNGP15.phx.gbl...
> Dist = 1. LogReader = 2.What is this anyways?
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:ualE1ms3EHA.3388@.TK2MSFTNGP15.phx.gbl...
> switched
> own.
>
|||I had a scheduled stop/ restart of the agents early this morning. Don't know
why that fixed it but it did. I know these were alreay being used because
last Sunday morning replication was timing out using the defaults but not
with mine. Anyways, thanks once again for the help.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:#Q47ou33EHA.3596@.TK2MSFTNGP12.phx.gbl...
> 0 means no history is logged and you should be running with 0 for
> performance reasons. 1 means minimal logging, 2 means more logging and 3
> means verbose. Verbose should only be used for debugging because it
degrades
> overall performance. 1 will only display the last historical record in the
> agent dialog. For instance when you drill down on the agent, it will show
a
> history of the activity - connecting to publisher, connecting to
subscriber,
> 23 transactions and 23 commands replicated. You will be unable to drill
> down any further. Setting the history to 2 will allow you to drill down
and
> see more historical information on the messages, ie a list of transactions
> and commands delivered in the past.
> However - I am bewildered by why you are not seeing any historical
> information. With the HistoryVerboseLevels you have you should be seeing
> information. Can you perhaps bounce these agents and see if the bounce
will
> fix the problem? If you make changes to the profile or the agent
parameters
> they will only be effective when the agent is stopped and restarted.
> There is also a condition where the buffers are depleted/exhausted that
the
> agents use to connect to SQL Server with and they hang in a perpetual
state
> of connecting/initializing. In my lifetime, I have only seen this once,
and[vbcol=seagreen]
> on this newsgroup I think I have seen it a couple of times - so it is
> relatively rare. You will have to reboot your machine to clear this
> condition.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> "ChrisR" <bla@.noemail.com> wrote in message
> news:%23wu703s3EHA.2336@.TK2MSFTNGP15.phx.gbl...
msdistribution_history[vbcol=seagreen]
I
>