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
>