Importing data into Excel from Databricks over ODBC OAuth / Simba Spark Driver

[Michael_Galli]

Hi all,
I am refering to this article
Connect to Azure Databricks from Microsoft Excel - Azure Databricks | Microsoft Learn

I use the latest SimbaSparkODBC-2.8.2.1013-Windows-64bit driver and configured in like in that documentation.
In Databricks I use a Serverless Warehouse (Current, v 2024.25)
I use Windows 11, Excel version 2403

Now when filtering data in Excel - Power query on that warehouse, in the Databricks query history I get the following error:

[UNBOUND_SQL_PARAMETER] Found the unbound parameter: _753. Please, fix `args` and provide a mapping of the parameter to either a SQL literal or collection constructor functions such as `map()`, `array()`, `struct()`. SQLSTATE: 42P02; line 36 pos 18

The query looks like this -> note the "?"

select
  `COLUMN1`,
from
  `catalog`.`schema`.`table`
where
  `PERIOD` = ?  and `PERIOD` is not null

Any idea on how to fix this?

[raphaelblg]

Hi @Michael_Galli, I've never seen this scenario before. Given the fact you're using a MSFT tech stack I'd recommend opening a support ticket with MSFT. 

[Michael_Galli]

Can you provide a link please?

[raphaelblg · Accepted solution]

@Michael_Galli, MSFT team should evaluate, if they can resolve the issue they will. If determined to be a Databricks/Simba issue, Databricks team will get involved.

https://azure.microsoft.com/en-us/support/create-ticket

[Aydin]

Hi @Michael_Galli, we're currently experiencing the same issue. I've just asked our internal support team to raise a ticket with Microsoft but thought it would be worth reaching out to you. Have you had any luck resolving this issue?

[Michael_Galli]

Here is the resolution I got from Databricks support:
"The reason they changed the default value of EnableNativeParameterizedQuery to 0 in v2.8 is that Databricks DBSQL server does not support Prepare when using native parameterized queries, so SQLPrepare will have a regression if the Native parameterized query is turned on by default and used by Power BI. The PG team also noticed that you’ve also turned on the UseNativeQuery. If you can turn off this (set UseNativeQuery=0), then it should also fix the issue even if they do not set EnableNativeParameterizedQuery=1 . Please note EnableNativeParameterizedQuery=1 was enabled in v2.7.3, before that, the query will also break if UseNativeQuery=1 "
hope this helps..