firebird-automations
commented
4 years ago Commented by: Pedro Innecco (pmdci)
Screenshot of debugging process showing the bug raised by the Firebird ODBC driver.
Open firebird-automations opened 4 years ago
firebird-automations
commented
4 years ago Commented by: Pedro Innecco (pmdci)
Screenshot of debugging process showing the bug raised by the Firebird ODBC driver.
firebird-automations
commented
4 years ago 
irodushka
commented
7 months ago Hi there
Can anyone check if the version 3.0.0.8 (or later) has the same issue? I mean https://github.com/FirebirdSQL/firebird-odbc-driver/wiki
Submitted by: Pedro Innecco (pmdci)
Attachments: microsoft_firebirdODBC_bug_screenshot.jpg
We are using the ODBC driver to load data from Firebird SQL into an Azure database using Azure Data Factory.
For that, we created a Windows 10 VM on-premise, which can access the Firebird SQL, and installed the Azure Data Factory Integrated Runtime, which works as the gateway to surface data to Azure Data Factory.
We noticed that with a particular dataset, the ADF process crashes on the local VM. After long sessions with the Microsoft product team for Azure Data Factory, they managed to isolate the issue to a bug in the Firebird ODBC driver.
Here is what Microsoft has to say. I'd be happy to share more information if required, but I'm afraid I will not do so in a public forum.
\~\~\~\~
So we have figured out the root cause after several times' on-call with you (thanks for your patience!). Here are the summary:
- First, this is a crash issue of the using 3rd party driver: Firebird ODBC driver. The following gives the call stack from the crash dump. So this is a bug in the 3rd party driver.
- - BTW, this seems an obsolete driver which hasn't been updated since 2017.
- Second, as far as we know, the Firebird driver bug only happens when using C# ADO .Net ODBC with big data set. If using native version of ODBC, the issue doesn't repro. As ADF Copy activity is using ADO .Net ODBC, you would hit the driver issue.
- Based on the current situation, ADF Copy activity cannot work well on the problematic driver, and a workaround suggestion is to use SSIS or other tools that don't use ADO .Net ODBC. Sorry for the inconvenience.