Thanks, but this isn't exactly what I was talking about. I am more concerned with modifying the way inserts are applied on the server side. Here is the problem I am facing right now:
1.
Client AAA takes a week and makes changes to thier local database by uploading several files to the DomainBlob table (say 30 records get added each ~ 200K's worth of binary data in the DataBlobData image field).
2.
Client AAA syncs with the server and all 30 records get pushed to the server in one batch because there is no batching on the client side.
3. All 30 newly inserted records in the server side database end up with the same SYS_CHANGE_CREATION_VERSION.
4.
Client BBB syncs.
5. All 30 records are downloaded to
Client BBB in one batch because the default filter for SelectIncrementalInserts contains this where clause below with the condition in the fourth line (remember in step 3 all records ended up with the same value in this field).
JOIN CHANGETABLE(CHANGES dbo.DataBlob, @sync_last_received_anchor) CT
ON CT.[DataBlobId] = dbo.DataBlob.[DataBlobId]
WHERE (CT.SYS_CHANGE_OPERATION = 'I'
AND CT.SYS_CHANGE_CREATION_VERSION <= @sync_new_received_anchor
AND (CT.SYS_CHANGE_CONTEXT IS NULL
OR CT.SYS_CHANGE_CONTEXT <> @sync_client_id_binary)
So given this I was looking for a way to change the processing step 3. Is it possible to change the way the records are inserted in the server database so that each record gets a different (incrementing) value for the SYS_CHANGE_CREATION_VERSION? If I can do this then the batching I have setup will take effect and step 5 will pull down 6 batches of 5 records instead of one batch of 30.
