I guess the script is written for backwards compatibility but if we could guarantee FMP15 Server/Client would the sync perform better if it was using the Truncate Table function?

Even have it in a loop iterating thru table instead of having to switch context even, and reduce script steps. 

There are very few cases in MirrorSync when we delete all the records on a device, and only during certain initial sync scenarios - so it would have no benefit for the vast majority of the time.

Where were you thinking about using it?

No plans just scrolling thru the script saw the steps and just thought candidate for new function

 

For what it's worth, you get this behavior for free if all the requirements are met. FM does a quick check to see if it can do this to increase performance. That check involves looking for and open/locked records, any cascading deletes or dependencies in the schema, and if you are in a found set of all records. If all conditions are met, it will functionally truncate the table for you, saving a load of time

Good to know, thanks Mike