B
BenO
Hi,
One of my colleagues is using BCM over-seas and is trying to synchronize
with our main database on SQL Server (on Windows 2003 server). We are in
Canada and he is in China.
Since he wants to be able to use the database offline, he is trying to build
the offline database on his computer. Everything appears to be working, but
after 3 minutes+ of synchronization, the process fails and BCM tells him to
try again. Sometimes, after rebooting his computer the process works, but it
is very unreliable and time consuming.
Is it possible that the slow network connection is causing this? When he
"pings" the server, the response time is about 623ms. Is it possible to
set-up the communication timeout for SQL Server and BCM? In SQL Server, I
can see that the "Remote query timeout" is set to 600 seconds for the server
and the "Keep alive" timeout is 30 seconds. I will try with 60 seconds, but
I would like to know if there is some similar setting in BCM directly.
Thanks for your help,
BenO
One of my colleagues is using BCM over-seas and is trying to synchronize
with our main database on SQL Server (on Windows 2003 server). We are in
Canada and he is in China.
Since he wants to be able to use the database offline, he is trying to build
the offline database on his computer. Everything appears to be working, but
after 3 minutes+ of synchronization, the process fails and BCM tells him to
try again. Sometimes, after rebooting his computer the process works, but it
is very unreliable and time consuming.
Is it possible that the slow network connection is causing this? When he
"pings" the server, the response time is about 623ms. Is it possible to
set-up the communication timeout for SQL Server and BCM? In SQL Server, I
can see that the "Remote query timeout" is set to 600 seconds for the server
and the "Keep alive" timeout is 30 seconds. I will try with 60 seconds, but
I would like to know if there is some similar setting in BCM directly.
Thanks for your help,
BenO