03-04-2011 08:55 AM
We've got a fairly decent sized database at our European office. It's holding 50000+ contacts and weighs in at around 3Gb (with attachments)
Previously our sales guyshad RDB's that were split in to sectors so kept the remote's fairly small... They operated flawlessly like this for approximately 18 months.
Recently however, it was decided that the remotes should have full access to the entire database, attachments and all. Since rolling out these RDB's with full access, problems have slowly started to creep in both for the remote users and even more bizarrely the local users, the local problems include and are not limited to;
- The SQL Database instance is unavailable
- Error – Note could not be created. One or more of the Contacts or Associations may have been deleted
- Object reference not set to an instance of an object
Then... the remotes, well... They cannot sync. The sync begins, and connects, but gets stuck at "Sending database modifications" - It's sits there for an hour and then times out. The sync log just gets as far as;
======== SYNC SESSION - 03/03/2011 07:48:26 ========
[ Info | 01/03/2011 07:48:26 ]Message: Synchronization started.
[ Info | 01/03/2011 07:48:26 ]Message: Server object created.
[ Info | 01/03/2011 07:48:27 ]Message: Checking if schema changes are available for sync.
[ Info | 01/03/2011 07:48:32 ]Message: Server establishing synchronization with remote database: LUC
[ Info | 01/03/2011 07:48:32 ]Message: Server generated remote sync session identifier: 364c040f-7dc8-4be0-9ed6-4f59e023128b:<LUC>
[ Info | 01/03/2011 07:48:37 ]Message: Checking if data changes are available for sync.
[ Info | 01/03/2011 07:49:07 ]Message: Server initialized database send session: 39
[ Error | 01/03/2011 08:49:08 ]Message: Server initialization failed. Synchronization timed out.
Any ideas? Suggestions? Life saving tips?
03-04-2011 10:22 AM
The bigger the database, the more frequently you need to sync. A database that size, I would sync at least daily, possibly more.