History Logging

How does the historyverboselevel and transactionsperhistory correlate ? If i
change the historyverbose level to 3 for the distribution agent profile, do
i also need to increase the transactionsperhistory ? I dont follow what the
transactionperhistory is.
Also the agents can log to output file based upon
http://support.microsoft.com/default...;en-us;312292. Is this
similar to changing the historyverboselevel to 3 or are the outputs totally
different between what is captured in the output file and setting it to 3
I am trying to gather some info about certain latency issues that we are
seeing between the time the record is inserted on the publisher and the time
it shows up on the subscriber and wanted to capture some logs.
Is this the right way ?
HistoryVerboseLevel refers to how much history is logged, 0 means none,
1 means only the current history or status is logged, overwriting any
past history, 2 is verbose, 3 is even more verbose and is used for
debugging.
TransactionsPerHistory controls how often the history is logged. So if
you have a value of 100 for TransactionsPerHistory you will not get any
history logged until your distribution agent stops or your distribution
agent distributes 100 transactions.
Hassan wrote:
> How does the historyverboselevel and transactionsperhistory correlate ? If i
> change the historyverbose level to 3 for the distribution agent profile, do
> i also need to increase the transactionsperhistory ? I dont follow what the
> transactionperhistory is.
> Also the agents can log to output file based upon
> http://support.microsoft.com/default...;en-us;312292. Is this
> similar to changing the historyverboselevel to 3 or are the outputs totally
> different between what is captured in the output file and setting it to 3
> I am trying to gather some info about certain latency issues that we are
> seeing between the time the record is inserted on the publisher and the time
> it shows up on the subscriber and wanted to capture some logs.
> Is this the right way ?
>
>
|||What about the output file ? Is that a different kinda logging of history ?
Do i need to set the verbose to 2 or 3 and also specify the output file ?
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:u%23hHynKPFHA.3388@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> HistoryVerboseLevel refers to how much history is logged, 0 means none,
> 1 means only the current history or status is logged, overwriting any
> past history, 2 is verbose, 3 is even more verbose and is used for
> debugging.
> TransactionsPerHistory controls how often the history is logged. So if
> you have a value of 100 for TransactionsPerHistory you will not get any
> history logged until your distribution agent stops or your distribution
> agent distributes 100 transactions.
> Hassan wrote:
If i[vbcol=seagreen]
do[vbcol=seagreen]
the[vbcol=seagreen]
totally[vbcol=seagreen]
3[vbcol=seagreen]
time[vbcol=seagreen]
|||the history is the history of your run, ie 10 transactions, and 20
commands. The output is far more detail. You can see the history in your
agent details. Output can only be read when it is piped to an output
file. You need to set OutputVerboseLevel to read these output statements.
Hassan wrote:
> What about the output file ? Is that a different kinda logging of history ?
> Do i need to set the verbose to 2 or 3 and also specify the output file ?
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:u%23hHynKPFHA.3388@.TK2MSFTNGP10.phx.gbl...
>
> If i
>
> do
>
> the
>
> totally
>
> 3
>
> time
>
>