cancel
Showing results for 
Search instead for 
Did you mean: 

Limit rows send to consolidate db from remote db with mobilink

Former Member
0 Kudos

I need to limit the rows that send the remote database to the consolidate database with mobilink 16.

I have a case that only need to send the rows for a table that only exists in another table to the consolidate database.

Also after the syncronization need to delete those rows in the remote database.

My consolidate DB and Remote DB is ASA 16.  I use for the syncronization mobilink 16.

Anyone have an idea how to resolve this case?

Thanks for any  help.

Accepted Solutions (0)

Answers (2)

Answers (2)

ddeconin
Advisor
Advisor
0 Kudos

2 other pointers that might be useful to limit data during upload

- Where clause in a publication : Only simple intra table clauses, so not useful if you need to join with another table, but then you might want to use a trigger on the 'other' table to maintain a 'sync/don't sync' flag on the table that you need to upload & then use a publication.

- Discard the unwanted rows on upload_insert & upload_update. Yes, this will upload the data to the server before discarding it, but depending on the  ratio between to upload & not to upload this might be simpler to maintain. (Perhaps use compression on the upload stream to compensate)

Not 100% sure they are valid solutions to your case , but they might be easier to maintain then the scripted upload.

former_member182948
Active Participant
0 Kudos

Hi Julio,

The log-based synchronization(default) will upload all client changes.

So, I think that you will need to use the "Scripted upload" instead of "log-based synchronization".

Using "Scripted upload" you can define what data you want to upload.

Please see the next document about the scripted upload.

http://dcx.sap.com/index.html#sa160/en/mlclient/mc-scriptbased.html

***You should take care to "Caution" of the above document.***

Caution

When you implement scripted upload, dbmlsync does not use the transaction log to determine what to upload. As a result, if your scripts do not capture all changes, data on remote databases can be lost. For these reasons, log-based synchronization is the recommended synchronization method for most applications.

Thanks