In DMF parameter there is a control for how data is inserted to staging table from uploaded file (or from integration queue). The control "Data Access Mode" has these two possible settings:

Table or view (Fast load)

Table of View

Fast load is the default setting and what it does is add two things to the insert statement via DIXF/SSIS logic: (check constraints, with tablock). This is prudent and efficient since best practice dictates that bulk insert operations are faster when doing a full table lock.

However it is not recommended in parallel processing with smaller payloads where full table locks might slow down performance due to the processing of data starting at the same time as inserts (causing wait times of LCK_MX and delays for inserting into staging table).

When using recurring integration there are many scenarios where parallel processing is of the essence, but since this parameter is global there is no way to currently adhere to best practices for all integration scenarios, either we use bulk insert with table lock globally or we don't.

My suggestion is to either provide this parameter per DMF project, or have it as part of the "Run messages in order" control on DMF recurring integration batch jobs. This will allow for better parallel processing where needed and still allow for bulk inserts of larger payloads to use the table lock for improved performance.

The change will have to be made in DMF components on SSIS as well as having this parameter per DMF project.