My IT department tried to set up a connection to IBM DB2 but could only get it to work through ODBC. This doesn't seem right. Also, the performance over ODBC is horrible. Trying to filter a multi-million row table takes forever (almost literally). Our DB2 database is on a mainframe (z/OS). Can anyone tell me what I should tell my IT department so that they can establish a proper connection to the IBM DB2 database? I assume that a proper connection exists (otherwise why would Microsoft list it as a valid connection option) and that such a proper connection would perform acceptably. My thought is that the ODBC route is a bad, although technically functional, approach.
Have you tried the built-in DB2 connector with Microsoft implementation? (IBM DB2 dialog > Advanced Options)
From the issues we've seen in customer scenarios, DB2 ODBC driver has a lot of incompatible behaviors when running against a z/OS instance.
Also, if you can send the traces to us (email@example.com) (Enable tracing from Options > Diagnostics > Enable Tracing (Verbose) (also you can open the Traces folder from here), then reproduce the failure, then close the PBI Desktop. You can get the traces from Traces folder.) we can see which step is taking long & might have some tips.
For example, if you're not using relationship columns, you can turn off "Include relationship columns" in the advanced settings.
Thank you for the reply. I have emailed the Trace info. Also, I have tried using Microsoft's built-in connector. However, I get the following error when I try that:
Unable to Connect
We encountered an error while trying to connect.
Details: "Value cannot be null.
Parameter name: sourceArray"
Fantastic, thank you. Hopefully "soon" means really, really, really soon
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.
October was a busy month in the community. Read the recap article to learn about some of the events and content.
Exciting news: We've given our badges an overhaul and added brand news ones.
Next in our Triple A series: Ask Amir Netz questions about the latest updates, features and future.
Experience a limitless analytics service built to ingest, prep, manage, and serve data for immediate use in Power BI.