I have a rather complex download_delete cursor. It contains a lot of SQL joins and performance isn't optimal on the consolidated db. I would like to simplify this, but this would result in fetching records (for deletion) that have never been downloaded to the remote database. Is this a problem for Mobilink?
asked 11 Aug '15, 07:15
This will create more data in the download stream (since the primary key of the rows that don't exist will also be sent) and will also result in the MobiLink client executing a "delete from table where pkey=X" for rows that don't exist at the remote when it applies the download stream. This means the time to write the download stream to the wire will be longer, and the time to apply the download stream at the remote will also be longer.
You should test whether the performance gains from the re-write of the download_delete_cursor are worth the extra time needed to write more data to the stream and apply the download.
answered 11 Aug '15, 09:16