• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 546
  • Last Modified:

Mobilink Synchronization (upload) of existing data in remote database.

We are trying to use Mobilink to synchronize our Corporate database with remote databases located at various regional offices.

We already have existing data in the regional databases. The problem we are facing is that when we are running synchronization, it is synchronizing only the new inserts done after the creation of Publications & Subscriptions.

What we want is to get all existing data from the regional databses and synchorinize our corporate databse with them. We are not able to do that.

Can anyone help us in doing the same.

Regards,
Anuj Paul.
0
antu23
Asked:
antu23
1 Solution
 
grant300Commented:
Anuj,

You are doing this implementation in kind of reverse order.  Normally you start with the consolidated database and migrate the schema (and any data) out to the virgin remote databases.  When you use the Migrate Schema wizard in Sybase Central, there is a checkbox option to the last page to "Migrate Data" when you migrate the schema.  After that, the data goes either direction depending upon the Pubs and Subs you have defined.

In the this case you have established remote databases and are trying to build a consolidated database.

Which way did you migrate the schema, remote to consolidated or consolidated to remote?

You can try to trick the system into sending all the data:
1)  Backup up everything!
2)  Break the Pubs/Subs for that remote server
3)  Delete the data for Region A from the consolidated server
4)  On the Region A server, copy the data into working tables (select into)
5)  Reconnect the Pubs/Subs for Region A
6)  On the Region A server, insert/select the data from the working tables back into the real tables
7)  Let it connect and then sit back and wait for the sync to finish.  Could take awhile.

8) - 800)  Repeat the above steps for each Regional Server.  Yuck!

Another approach that MAY be possible depends on two things: do you have a Pub/Sub for UPDATES and do you have the update logic on the consolidation server setup to INSERT a record that was updated on the Remoe server but is not found in the consolidated server.

If both these conditions are true you can do a meaningless  update (with no where clause) against each table.  Mobilink should pick it up and move it but it will be ugly as well.

Yet a third option is to dump the tables at the remotes databases into flat files, move them to the consolidated site, and load them in the server.  You will have to figure out how to delete any data that already exists for the Regional server you are loading at the moment.  This is probably the most effeciant method since it bypasses the overhead of replication.  You just have to find adequate batch window to get the extract, transfer and load done.

Hope that helps.

Bill
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now