Hello
When i am Synchronizing(SQL2005 merge replication)
I can see the duration of the Synchronization on the Replication
monitor and i can see that lets say an "initial loading" of the
database with lots of data is taking 4 minutes but on the handheld if i
take the time of the Synchronize() command that can take up to 30
minutes.
Why is this happening? Am I doing something wrong here?
Thanks
Savvas Christodoulou
The replication monitor shows the time it took for the server side
reconciler to write the initial data to the .OUT file in the IIS server.
The writing of the OUT file to the device can take longer depending on your
network connection etc.
<savvaschr@.nodalsoft.com.cy> wrote in message
news:1162307433.787568.183190@.e3g2000cwe.googlegro ups.com...
> Hello
> When i am Synchronizing(SQL2005 merge replication)
> I can see the duration of the Synchronization on the Replication
> monitor and i can see that lets say an "initial loading" of the
> database with lots of data is taking 4 minutes but on the handheld if i
> take the time of the Synchronize() command that can take up to 30
> minutes.
> Why is this happening? Am I doing something wrong here?
> Thanks
> Savvas Christodoulou
>
|||Thanks a lot ,
I finaly understood what was going on just after i post this message.
Regards
Showing posts with label duration. Show all posts
Showing posts with label duration. Show all posts
Wednesday, March 7, 2012
Saturday, February 25, 2012
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
>
>
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
>
>
Subscribe to:
Posts (Atom)