Friday, March 9, 2012

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

No comments:

Post a Comment