Forum Discussion
IBM DB2 vs ODBC
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.
11 Replies
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 protected]) (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"That looks interesting. Can you please send us traces for that error too?
Thanks
