Support for ODBC Data Destinations via On-Premises Data Gateway

Enhancing data integration capabilities by adding ODBC data destination support.

Use Case:

I am working with a legacy application for which I have no access to the source code, making it impossible to modify or update. This application relies on a database that supports ODBC connections. My goal is to feed data from Business Central, prepared within Fabric, into a specific table in this application’s database.

Currently, Fabric allows using an on-premises SQL Server as a data destination via the on-premises data gateway, but it does not support ODBC data destinations.

While it’s possible to implement a workaround by first pushing the data to an on-premises SQL Server and then replicating it to the application’s database, this approach is inefficient and adds unnecessary complexity to the data integration process.

Benefits:

• Expanded Compatibility: Supporting ODBC data destinations would enable integration with a broader range of databases, including those used by legacy systems that cannot be modified.

• Improved Workflow Efficiency: Directly writing data to the legacy application’s database eliminates the need for complex and time-consuming workarounds.

• Increased Flexibility: Users can connect to any ODBC-compliant database, providing greater flexibility in handling various data environments.

Proposal:

I propose that Fabric extends its data destination capabilities to include support for ODBC connections via the on-premises data gateway. This enhancement would allow users to write data directly to any ODBC-compliant database, significantly improving integration with legacy systems and expanding the utility of Fabric in various data environments.

Thank you for considering this feature request.