Importing tabular data in an Excel sheet to SQL server seemed is processed by row. It will be great if there is a batch mechanism as the mapping from Excel to SQL only needs to be defined once. Many of our Excel sheets take four hours to import. Potentially, batch loading can improve the loading speed.
When I had multiple Excel sheets that needed to be loaded to the same table, I was not sure whether the parallel loading may mess up something accidentally, say to miss or duplicate a row. Therefore, I spent a lot of time babysitting it to manually trigger the flow so only one file was loaded at a time. It will be cool if there is a way to configure a flow such that if there are many flow triggers, the triggers are automatically queued to be processed sequentially.