Replication Test\Check 6.5 & 2000 are in sync

Hi,
I am having MSSQL 6.5 with batch driven transactions
I am upgrading to 2000 and plan to do some black box
testing.
To test the batch jobs,I am planning to run the job on 6.5
and 2000 and test the rowcounts and records added/updated
based on datetime.(I don't have delete..so checking the
data on the basis of timestamp works)
However my rowcount and timestamp queries take a long time
to run on 6.5.(More than 50 mins as data volume and no of
tables are high)
I can't wait that long as the production server 6.5 has
jobs that run after every 30 mins.Is there a way just to
check whether 6.5 and 2000 data are in sync using some
built in utility or better algortithm(I don't want to
compare using SQL,but comparison at the lower level such
as file etc would do)
Basically do something like what replication or mirroring
does but not actually move the data but just check
Thanks
RakeshTake a look at the sp sp_replcounters... It shows how many records in the
log are awaiting replication...
"ar" <ambewadkarrakesh@.johndeere.com> wrote in message
news:05fb01c344f6$cb8265b0$a501280a@.phx.gbl...
> Hi,
> I am having MSSQL 6.5 with batch driven transactions
> I am upgrading to 2000 and plan to do some black box
> testing.
> To test the batch jobs,I am planning to run the job on 6.5
> and 2000 and test the rowcounts and records added/updated
> based on datetime.(I don't have delete..so checking the
> data on the basis of timestamp works)
> However my rowcount and timestamp queries take a long time
> to run on 6.5.(More than 50 mins as data volume and no of
> tables are high)
> I can't wait that long as the production server 6.5 has
> jobs that run after every 30 mins.Is there a way just to
> check whether 6.5 and 2000 data are in sync using some
> built in utility or better algortithm(I don't want to
> compare using SQL,but comparison at the lower level such
> as file etc would do)
> Basically do something like what replication or mirroring
> does but not actually move the data but just check
> Thanks
> Rakesh

replication monitor error

When Replication monitor shows an error icon, I removed all the publication jobs completedly. After I reconfigured publishing, subscriber,Distribution, why the replication monitor still shows an error icon even though there is no replication job scheduled?

Thank you!

Thanks for using replmonitor.

Would you like provide more detailed repro steps? like how do you remove publicaiton jobs, delete jobs under sqlserveragent, or remove subscriptions? How did you reconfigure everything, did you disable distribution and publication, then recreate them?

Thanks

Yunjing

|||My problem has been resolved by restart sql server agent. Thank you!

replication monitor error

When Replication monitor shows an error icon, I removed all the publication jobs completedly. After I reconfigured publishing, subscriber,Distribution, why the replication monitor still shows an error icon even though there is no replication job scheduled?

Thank you!

Thanks for using replmonitor.

Would you like provide more detailed repro steps? like how do you remove publicaiton jobs, delete jobs under sqlserveragent, or remove subscriptions? How did you reconfigure everything, did you disable distribution and publication, then recreate them?

Thanks

Yunjing

|||My problem has been resolved by restart sql server agent. Thank you!

replication log reader failed

Hi all,
Sql server 7.0
I have replication jobs which replicates the data from one
server to another.
one of our server was down for some duration of time and
the replication job log reader has failed it gives the
error msg log reader agent: "the process could not
execute 'sp_repldone/sp_replcount".
pls help me in solving this problem.
TIA
Haseeb,
I thought these issues had been sorted in SP>=2. If you don't have it
installed it's worth putting on. Either way, you could try increasing the
Query timeout (default: 300 seconds) on the logreader by editing the
QueryTimeout option as this is I think the issue.
HTH,
Paul Ibison
|||I also had this problem and setting the QueryTimeout did not help. I tried everything in every posting I could find and nothing worked. I ended up deleting all my publications to reset the Log Reader Agent, then re-setup the publications and subscriptio
ns. Once the Log Reader was recreated, everything worked fine again.
"Paul Ibison" wrote:

> Haseeb,
> I thought these issues had been sorted in SP>=2. If you don't have it
> installed it's worth putting on. Either way, you could try increasing the
> Query timeout (default: 300 seconds) on the logreader by editing the
> QueryTimeout option as this is I think the issue.
> HTH,
> Paul Ibison
>
>

Replication jobs owned by sa

The reason sa is often suggested as the owner of
replication jobs is that when the job runs, there is an
active directory lookup performed of the job owner. This
is the reason sa is used - no AD lookup required. The
jobs themselves are run under the authority of the sql
server agent so trusted/non-trusted security doesn't
really apply, as windows logins are always authenticated.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
So are you saying , that even when i change the authentication mode to
Windows only , the jobs will still run even if they are owned by sa
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:170001c4e8d4$3eea74c0$a501280a@.phx.gbl...
> The reason sa is often suggested as the owner of
> replication jobs is that when the job runs, there is an
> active directory lookup performed of the job owner. This
> is the reason sa is used - no AD lookup required. The
> jobs themselves are run under the authority of the sql
> server agent so trusted/non-trusted security doesn't
> really apply, as windows logins are always authenticated.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Correct. The owner of the job is not the login used to
run it, as this is a cmdexec type of job and therefore
runs as the agent.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

replication job failure

Our SQl Server 2000 was rebooted recently but when I check the management
section then jobs replication its registered as failed yet when checking the
history it is still executing step 2.
Yet when I check in the replication monitor in the distribution agents
replication is as normal do you know how I can get rid of the fail status if
it is still processing transaction replication that has been running for 3
days on step 2?
thanks for any help
Sammy
Sammy,
you could try stopping and restarting the job, then refresh.
Rgds,
Paul Ibison
|||Thanks Paul it worked
"Paul Ibison" wrote:

> Sammy,
> you could try stopping and restarting the job, then refresh.
> Rgds,
> Paul Ibison
>
>