Specific actions required after upgrading to MS SQL 2017

[Wolverine]

The environment in this case is a single server implementation. Our DBA just completed the upgrade from MS SQL Server 2014 to MS SQL Server 22017. Now that the upgrade is complete, we are NOT able to get valid test results from the data sources.

Through Cognos Connection, we are NOT able to run any of the stored (previously working) reports. Even in the 'Cognos Administration' tool, we are not able to test the 'Data Source' connection. We get the same error message. Are data connections are based on "Microsoft SQL Server (SQL 2012/2014 Native Client)".

Does anyone know how to validate the existing SQL driver in use?

What is the 'Best Practice' method to connect to MS SQL Server 2017? Should we change to Microsoft SQL Server (OLE DB)? or Microsoft SQL Server (ODBC)?

Any experience/help with this will be helpful.

Thanks!

[dougp]

Can you say, "Duct tape and bailing wire?"

You're using Cognos 10 and trying to run it with SQL Server 2017?  I don't see SQL Server 2017 listed anywhere in the Cognos Business Intelligence 10.2.2.0 Software Product Compatibility Reports all the way through 10.2.2.9 - the last maintenance level for the product.  I think you have two options:

• tell your SQL DBAs that they can't upgrade any servers that are used for or by Cognos
• upgrade to Cognos Analytics

SQL Server 2017 is supported beginning in Cognos 11.0.10.  I'd recommend waiting for Cognos 11.0.13 LTS to be released.  Probably October.  Then installation process testing, content testing, user acceptance testing, emails, leaflet canvassing, more emails, broadcast phone messages, announcements in "all staff" meetings, yet more emails...  then everyone will still complain that the upgrade was a surprise.  Good luck.

[Wolverine]

THANKS!

[bdbits]

You might be able to get it working, but as was pointed out it is unsupported.

The first thing I would check is whether the server name was changed. That would be a connection string change.

The second would be whether they compatibility level of the particular database was left at 2014. I think there would be less chance of connecting successfully if this was not left at 2014.

[Wolverine]

Good news for those following this thread.... Cognos 10.2.2 operates with MS SQL Server 2017 for both the Content Store and the data sources.

Our issue was that the SQL Client was removed from the server during a maintenance upgrade. Once SQL 2017 Client was reinstalled all was good!

[cognostechie]

This does not mean that it will work for anybody having 10.2.2 and SQL 2017. If it is not supported , it not guaranteed. It might be working in one environment because of a number of other factors and may not work in another environment.

I am posting this so that people don't take your results as granted and jump for it and then get misled.

[jcw3631]

According to IBM if its not on the software compatiblity list, all that means is they haven't tested that piece of software.  It could work or not work.

[MFGF]

According to IBM if its not on the software compatiblity list, all that means is they haven't tested that piece of software.  It could work or not work.

...and also it means that if you have Extended Support and try to log a support call, IBM will insist you replicate the issue using a supported database before they will be able to help. All in all it's not a wise strategy to move to an unsupported environment (in my humble opinion).

:)

MF.