10,730
edits
Important: Deprecating old WebView — Publish failed error
Releases/Winter 2020: Difference between revisions
Jump to navigation
Jump to search
→Synchronization: potential performance saver
No edit summary |
|||
| Line 64: | Line 64: | ||
=== Synchronization: potential performance saver === | === Synchronization: potential performance saver === | ||
Advanced sync setup ( | Advanced sync setup (in the sync config file) now offers an additional option, primarily for Dynamics users. | ||
You can now configure incremental sync to not sort records by the versionnumber field. Microsoft recommends using versionnumber sorting as it greatly improves the performance of some fetches. However, our tests show that in some cases, it has the opposite effect. Setting on/off this flag can change fetch performance from minutes to a fraction of a second - or vice versa. The reason apparently lies in the SQL server setup (definition of indexes, etc.) and cannot be predicted. Use this flag as the last resort if you have an extremely slow fetch in incremental sync. See [[Advanced_sync_setup#Disabled_sorting_by_version_number|Disabled sorting by version number]] for more information. | You can now configure incremental sync to not sort records by the versionnumber field. Microsoft recommends using versionnumber sorting as it greatly improves the performance of some fetches. However, our tests show that in some cases, it has the opposite effect. Setting on/off this flag can change fetch performance from minutes to a fraction of a second - or vice versa. The reason apparently lies in the SQL server setup (definition of indexes, etc.) and cannot be predicted. Use this flag as the last resort if you have an extremely slow fetch in incremental sync. See [[Advanced_sync_setup#Disabled_sorting_by_version_number|Disabled sorting by version number]] for more information. | ||