Author Topic: SQL JDBC drivers  (Read 650 times)

Offline oscarca

  • Community Leader
  • *****
  • Join Date: Jul 2018
  • Posts: 210
  • Forum Citizenship: +0/-0
SQL JDBC drivers
« on: 30 Sep 2019 10:20:25 am »
Does anyone here use Microsoft Analysis Services 2017 and if so what SQL JDBC drivers do you use ?
On my PROD server I use Microsoft Analysis Services 2014 with sqljdbc42.jar driver which works great, but for some reason I cannot connect to 2017 version when creating the Data source in Cognos Administration.

Best regards,
Oscar

Offline MFGF

  • Never knowingly correct
  • Super Moderator
  • Statesman
  • ******
  • Join Date: Jul 2005
  • Posts: 10,849
  • Forum Citizenship: +647/-10
  • Cognos Software Muppet
Re: SQL JDBC drivers
« Reply #1 on: 30 Sep 2019 10:50:29 am »
Does anyone here use Microsoft Analysis Services 2017 and if so what SQL JDBC drivers do you use ?
On my PROD server I use Microsoft Analysis Services 2014 with sqljdbc42.jar driver which works great, but for some reason I cannot connect to 2017 version when creating the Data source in Cognos Administration.

Best regards,
Oscar

Hi,

What version of Cognos Analytics are you using? It looks like MSAS 2017 is supported in 11.0.13 and in all the 11.1 versions, but not prior versions to 11.0.13

https://www.ibm.com/support/pages/ibm-cognos-analytics-1100-supported-software-environments

Cheers!

MF.
Meep!

Offline oscarca

  • Community Leader
  • *****
  • Join Date: Jul 2018
  • Posts: 210
  • Forum Citizenship: +0/-0
Re: SQL JDBC drivers
« Reply #2 on: 30 Sep 2019 03:13:59 pm »
Hello MF

I use Cognos Analytics 11.1.2.

Cheers!

Offline MFGF

  • Never knowingly correct
  • Super Moderator
  • Statesman
  • ******
  • Join Date: Jul 2005
  • Posts: 10,849
  • Forum Citizenship: +647/-10
  • Cognos Software Muppet
Re: SQL JDBC drivers
« Reply #3 on: 01 Oct 2019 08:53:11 am »
Hello MF

I use Cognos Analytics 11.1.2.

Cheers!

In that case it ought to work. I don't use MSAS so I can't help you with specific advice here, sorry. Have you logged it with IBM?

MF.
Meep!

Offline oscarca

  • Community Leader
  • *****
  • Join Date: Jul 2018
  • Posts: 210
  • Forum Citizenship: +0/-0
Re: SQL JDBC drivers
« Reply #4 on: 01 Oct 2019 09:54:15 am »
Haven't logged it with IBM, thought I would check with my fellow cognoise people  :)
Thanks anyways MF !

Offline MFGF

  • Never knowingly correct
  • Super Moderator
  • Statesman
  • ******
  • Join Date: Jul 2005
  • Posts: 10,849
  • Forum Citizenship: +647/-10
  • Cognos Software Muppet
Re: SQL JDBC drivers
« Reply #5 on: 01 Oct 2019 10:27:20 am »
Haven't logged it with IBM, thought I would check with my fellow cognoise people  :)
Thanks anyways MF !

It looks to me like sqljdbc42.jar is the correct one for the version of Java that ships with CA, but have you checked to see that there isn't another java version installed that is conflicting?

Cheers!

MF.
Meep!

Offline oscarca

  • Community Leader
  • *****
  • Join Date: Jul 2018
  • Posts: 210
  • Forum Citizenship: +0/-0
Re: SQL JDBC drivers
« Reply #6 on: 04 Oct 2019 03:01:08 am »
That is the only driver that is placed in the "Drivers" folder. Do you think it could be a driver on the test server for SSAS that could be the issue ?

Offline MFGF

  • Never knowingly correct
  • Super Moderator
  • Statesman
  • ******
  • Join Date: Jul 2005
  • Posts: 10,849
  • Forum Citizenship: +647/-10
  • Cognos Software Muppet
Re: SQL JDBC drivers
« Reply #7 on: 04 Oct 2019 06:48:21 am »
That is the only driver that is placed in the "Drivers" folder. Do you think it could be a driver on the test server for SSAS that could be the issue ?

I'm referring to the JRE that ships with Cognos Analytics. The driver is correct for the JRE version that CA ships with, but if you have another JRE installed and it's a different version, it might cause issues.

Cheers!

MF.
Meep!

Offline oscarca

  • Community Leader
  • *****
  • Join Date: Jul 2018
  • Posts: 210
  • Forum Citizenship: +0/-0
Re: SQL JDBC drivers
« Reply #8 on: 11 Nov 2019 09:29:21 am »
To get back at you with the status of the issue MF, I just wanted to say that it was actually not the driver that didnt work, it was an permission problem.
It is solved now thank you :)

Best regards,
Oscar

 


       
Twittear