If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

SQL Server 2014 support roadmap?

Started by EarthDog, 02 Apr 2014 02:03:38 PM

Previous topic - Next topic

EarthDog

Is there any indication as to when SQL2014 is gonna be supported?

I was ready to replace my DW server to 2012 but now SQL 2014 is out....

MFGF

You have to give IBM time to check conformance before they can release a version that supports SQL Server 2014. I'd imagine the next fix pack or version will be compliant, but that's my opinion and in no way indicative of IBM's plans - just a muppet being hopeful.

MF.
Meep!

EarthDog

i see...

And what could happen if i just use 2014 as my content store and datasource provider?

I mean by using the existing native client that cognos has...

MFGF

Quote from: EarthDog on 03 Apr 2014 09:06:38 AM
i see...

And what could happen if i just use 2014 as my content store and datasource provider?

I mean by using the existing native client that cognos has...

My guess is that you'd probably get away with using it as a content store, as access is via JDBC not the native client. For the data source I'm not so sure, though. When you set up a SQL Server connection you need to specify the type - Microsoft SQL Server (OLEDB), Microsoft SQL Server (SQL 2005 Native Client), Microsoft SQL Server (SQL 2008 Native Client) or Microsoft SQL Server (SQL 2012 Native Client). From my limited testing in the past, a SQL Server 2008 Native Client connection didn't work with a SQL Server 2012 database. I'd suspect the same is true if trying to access SQL Server 2014 using the SQL Server 2012 Native Client. You might try using JDBC instead - set up a SQL Server 2012 Native Client connection but with garbage in the native client fields and real values in the JDBC fields?

Other things to try might be ODBC connection too?

Notwithstanding, you wouldn't get support from IBM if things went wrong.

Cheers!

MF.
Meep!

EarthDog

My thoughts were similar to yours...

I think that i wil lstick with SQL Server 2008 R2 fo rthe moment and move my ETL jobs to another SSIS box with SQL 2014....

thanks for your comments.