Application Using Threads (ApplicationUsingThreads): The driver coordinates concurrent database operations (operations from different threads) by acquiring locks. Although locking prevents errors in the driver, it also decreases performance. If your application does not make ODBC calls from different threads, the driver has no reason to coordinate operations. In this case, the ApplicationUsingThreads attribute should be disabled (set to 0).
Note: If you are using a multi-threaded application, you must enable the Application Using Threads option.
Batch Update Chunk Size (BatchUpdateChunkSize): This option can impact performance by reducing the number of round trips required to complete an insert, update, or delete operation. For example, at the default setting of 200 rows, a 10,000 row insert operation would require 50 round trips. Setting Batch Update Chunk Size to 500 rows would reduce the number of round trips to 20.
Create Map (CreateMap): Create Map determines whether the driver creates the internal files required for a relational map of the native data when establishing a connection. When the driver creates these internal files, an initial connection can take a few minutes, depending on network speeds and the amount of metadata the driver must retrieve from the service. For example, when Create Map is set to 4 (OnChange), the default, and changes have been made to the Dynamics 365 back-end schema, the connection may be delayed because the driver runs a discovery on the Dynamics 365 schema and overwrites the internal files used to create a relational map of the data.
Fetch Size(FetchSize): Reducing the number of round trips on the network to the approximate number of rows being fetched increases performance. For example, if your application normally fetches 200 rows, it is more efficient for the driver to fetch 200 rows at one time over the network than to fetch 50 rows at a time during four round trips over the network.
