Can the SQL Server ODBC driver be adapted to use an alternative approach for creating multi-row insert statements into Microsoft Fabrics database?

The driver functions as expected, supporting parameterized inserts and transmitting data in a single batch. Specifically:

The parameterized array is packaged into a single TDS statement.
Network transmission occurs as a single operation, confirmed by packet logs.

However, on the Fabric database side, the behavior differs:

The query processor internally decomposes the parameterized array.
Each element is treated as a separate execution context.
Each context receives a unique distributed_statement_id and is logged as an individual operation.
Every execution context initiates its own Parquet file write.

This results in inserts being processed row-by-row on the Fabric database, despite being sent as a batch by the driver.

An enhancement request has been submiited as an Idea on the Progress Community. 

Customer feedback is valuable and Idea submissions are monitored by our Product Management team. Enhancement requests are reviewed during the planning phase of each new product release and a list of the enhancements chosen for implementation can be found in the Release Notes documents that accompany each release. Once an Idea is submitted the Progress Software Community will have the opportunity to comment on and vote for the Idea. It's priority will be evaluated as customer demand weighs in through Article Feedback and through vote count in the Ideas Portal.

For detailed information on how to submit an Idea, please refer to Knowledge Base article : How to submit an enhancement request for a Progress product?