Replication Distributor Job History is shocking!

Sorry for the odd format but that is what happens when you paste here! This is data from our Job History for a "Replication Distributor" Job Step Type. Here is how I interprete it: The job step started on the 19th. It restarted itself twice on the 20th. Then it restarted itself twice on the 21st. Then it restarted itself 3 times on the 22nd. And finally it restarted itself on the 23rd. Notice the progression of Retries_Attempted. When Retries_Attempted exceeds 10, the step will fail and the service will shut-down, which is what I have seen in the past. I conclude the Advanced Settings of Retry Attempts is not per "Event" but "total tries no matter how many successful retries are encountered." I thought a successful retry would reset the Retries_Attempted. But it does not. Is this correct? This implies that to keep the distributor up, we should set the Retry Attempts" setting to its max!

Status Run_Date Run_Time Run_Duration Retries_attempted

1

1/19/2007

44025

0

0

2

1/20/2007

31200

1429

1

2

1/20/2007

32729

234250

2

2

1/21/2007

31119

1558

3

2

1/21/2007

32817

234225

4

2

1/22/2007

31142

1513

5

2

1/22/2007

32755

508

6

2

1/22/2007

33403

233615

7

2

1/23/2007

31118

1503

8

2

1/23/2007

32721

501

9

Topping this one so I can remember it, will look into it.

Replication -- subscriber job history does not appear on SQL server 2005 Subscriber from S

Hi Everyone,
I have a small issue in looking at the the subscription's job history
(transaction history) on SQL Server 2005 subscriber subscribed to a
SQL Server 2000 publication.
We have the following environments set up and running and all the
Windows and SQL servers service packed to the latest. We are using
transactional replication with all pull subscriptions.
-----
Replication Publisher: SQL server 2000 Standard Edition(on Windows
2003 Server)
both publisher and distributor run on the same machine.
-----
Replication Subscriber: SQL server 2000 Standard Edition(on Windows
2000 Server)
both publisher and distributor run on the same machine.
-----
When I look on the subscriber SQL server 2000, in the subscription's
job history, a message (row) for each transaction (or one row for upto
a group of 100 transactions) is written along with start-up messages
for the job and any error messages.
But when we set up the subscriptions on SQL server 2005 from same
publication, as below
-----
Subscriber: SQL server 2005 Standard Edition(on Windows 2003 Server)
both publisher and distributor run on the same machine.
-----
the replication works fine but the job history is not consistent
between 2000 and 2005 subscribers. When I look on SQL server 2005
subscription's job history, no rows are written for the transactions,
but only messages are logged for job start-ups and any error messages.
Did anyone notice this behaviour?
Is there any way we can configure so all the transaction messages
appear in subscription's job history in SQL Server 2005.
Regards
Raj Chidipudi
On 6 Aug, 14:03, Raj Chidipudi <chidip...@.gmail.com> wrote:
> Hi Everyone,
> I have a small issue in looking at the the subscription's job history
> (transaction history) on SQL Server 2005 subscriber subscribed to a
> SQL Server 2000 publication.
> We have the following environments set up and running and all the
> Windows and SQL servers service packed to the latest. We are using
> transactional replication with all pull subscriptions.
> ----X--
> Replication Publisher: SQL server 2000 Standard Edition(on Windows
> 2003 Server)
> both publisher and distributor run on the same machine.
> ----X--
> Replication Subscriber: SQL server 2000 Standard Edition(on Windows
> 2000 Server)
> both publisher and distributor run on the same machine.
> ----X--
> When I look on the subscriber SQL server 2000, in the subscription's
> job history, a message (row) for each transaction (or one row for upto
> a group of 100 transactions) is written along with start-up messages
> for the job and any error messages.
> But when we set up the subscriptions on SQL server 2005 from same
> publication, as below
> ----X--
> Subscriber: SQL server 2005 Standard Edition(on Windows 2003 Server)
> both publisher and distributor run on the same machine.
> ----X--
> the replication works fine but the job history is not consistent
> between 2000 and 2005 subscribers. When I look on SQL server 2005
> subscription's job history, no rows are written for the transactions,
> but only messages are logged for job start-ups and any error messages.
> Did anyone notice this behaviour?
> Is there any way we can configure so all the transaction messages
> appear in subscription's job history in SQL Server 2005.
> Regards
> Raj Chidipudi
Resolved the issue by editing job used to run the subscription on the
subscriber.
Just suffixed this "-HistoryVerboseLevel [3] -OutputVerboseLevel [2]"
at the end of the command in the only job step.
But i must admit it needed a bit of digging-in few things.
Raj Chidipudi