Is MS SQL Server Native Client 2012 required

[jahill938]

We just finished transferring our Cognos Analytics to Windows Server 2016. Everything worked except an issue with the data sources. The java connections all came back successful but the native connections failed. Although it seemed to work correctly, there were connection issues particularly with the data source in Framework Manager. It took awhile but we did figure out we were missing sql server native client 2012. After installing the native client we got a successful connection.
We use Framework Manager on our development server to create the model and publish it to Cognos. We then export from our development server and import it into our production server.

My question is, is the 2012 native client needed only on our development server where the data sources are created and used with Framework Manager and the model then published to Cognos or does the 2012 native client also need to be installed on the production server?

[MFGF]

We just finished transferring our Cognos Analytics to Windows Server 2016. Everything worked except an issue with the data sources. The java connections all came back successful but the native connections failed. Although it seemed to work correctly, there were connection issues particularly with the data source in Framework Manager. It took awhile but we did figure out we were missing sql server native client 2012. After installing the native client we got a successful connection.
We use Framework Manager on our development server to create the model and publish it to Cognos. We then export from our development server and import it into our production server.

My question is, is the 2012 native client needed only on our development server where the data sources are created and used with Framework Manager and the model then published to Cognos or does the 2012 native client also need to be installed on the production server?

Hi,

If your packages and reports are using Compatible Query, you need the Native Client (32-bit) installed on the machine you use for FM and on each of your server instances - Dev and Prod. If you are not using Compatible Query, you just need the jdbc files to be present in the Drivers folder in each instance (Dev and Prod).

Cheers!

MF.

[jahill938]

Thank you for your response. It's been a while since we set everything up and I don't see where we set the query mode. I did confirm when I looked at the advanced properties of our FM published model that the query mode is set to Dynamic. However in FM I was still getting a connection error when the 2012 native client was not installed. Looks like I still need it on my Dev server but not on Production?

[cognostechie]

Hi

It has nothing to do with Dev or Production. It has to be installed to whichever server has FM installed on it regardless of whether it is Dev or Prod.

Normally, there is no reason for FM to be installed on any Prod server

[MFGF]

Thank you for your response. It's been a while since we set everything up and I don't see where we set the query mode. I did confirm when I looked at the advanced properties of our FM published model that the query mode is set to Dynamic. However in FM I was still getting a connection error when the 2012 native client was not installed. Looks like I still need it on my Dev server but not on Production?

The query mode is set in the Framework Manager model. If you are using Dynamic Query, all access is via JDBC on the server - including in FM, even when FM is on a different machine. If you are using Compatible Query, you need the native client installed on the machine running FM plus on every instance from a server perspective. This means if you have a Dev and a Production instance, you need the native client installed on both.

Cheers!

MF.