Forum Discussion
IBM DB2 vs ODBC
Thanks, we found where that error is coming, and will fix that soon. About the performance, I didn't see the ODBC traces. Can you try that again, and make sure you pick Verbose level?
Fantastic, thank you. Hopefully "soon" means really, really, really soon :smileyhappy:
How will I know when it's fixed?
I'm assuming this means once it's fixed I should be able to connect using the "IBM DB2 Database" option from the "Database" category of the "Get Data" dialog using the "Microsoft (requires .Net 4.5 or higher)" option under the "Advanced options" dropdown, correct?
I don't have the ODBC set-up yet on the machine I am using at the moment but I do have it on my machine at my home so I will generate the trace data on that tonight and email that you. (of course my hope is to eventually not have to use the ODBC approach)
We don't really have an ETA yet, it seems like an external issue. But, my guess, it probably won't take more than a few releases.
You'll know if it's fixed if someone updates this thread, or just start trying every new release in 2017 :) If there are no other issues, you should be able to use that "Microsoft" option.
I've just sent another email with the trace files related to poor ODBC performance. In Power BI Desktop I pulled 3 tables from DB2 and tried filtering one of the tables to show only rows with a transaction posting date between 1/1/2016 and 1/31/2016. After waiting for a very long time I just gave up and closed the program.
Oh, I just learned that this (Value cannot be null. error) was a known issue and it was already fixed :) It'll be out in (end of) October release.
I'll look into the traces about the performance, my guess is the driver reports us that its unable to compare dates, so we have to pull all the data.. I'll let you know once I take a look at them.