We are trying to use NMSP and having issues with the skip setting.
In the NMSP source data definition, we have a @Formula based select indicating which documents we want to process (this is normally based on a particular form name). Because some databases have many thousands of documents using a specific form, we wanted to use the 'skip' setting (along with the max records setting) in the console application to break the migration job into batches.
However, when investigating various performance issues, we did a trace of the NMSP <-> Lotus Notes/Domino conversation using notes.ini debug settings. In the trace file we notice that NMSP is still opening documents that we have told it to skip, i.e. if NMSP is configured with a skip setting of '10' and the max record is set to '10', we see in the trace that 10 documents are opened, but no actions appear to be performed. NMSP then processes documents 11 - 20 OK and then stops as expected. On the next run, when we change the skip setting to '20', NMSP still opens the first 20 documents before processing documents 21 - 30.
The opening of documents that are already migrated is resulting in more and more traffic between NMSP and Lotus Notes/Domino and making each run of the job take longer and longer.
Is it possible to configure NMSP to really skip the number of documents defined in the skip setting (i.e. not open them)?
Thanks.