Invertedflyby
Member
Hi All,
We are on the following:
Apps 9.0
TR 9.1.5.1
All Windows 2008 Servers
Weblogic 12.1.2
JDK 1.6
SQL 2008 R2
We would like to upgrade (swap) the database machine from Windows 2008 to Windows 2012 and SQL 2008 R2 to SQL 2014. This will be a hard cutover with the new machine retaining the old name.
The dilemma is, do I keep the same JDBC (sqljdbc4.jar) drivers and SQL Native Access Client 10? It appears that I should based on everything I have read, which I believe to be incomplete data.
It looks like SNAC 11 is not certified to work with SQL Server 2014. The new Microsoft ODBC Driver 11 is not certified on any OS below Windows 2008 R2. But I cannot find anything determining whether SNAC 10 is supported with SQL 2014. I cannot find anything to the contrary either. I suspect it would be fine since no new features in JDE are being introduced that would need to take advantage of any new functionality in SQL 2014. We already have FASTFIRSTROW disabled.
It does look like JDBC 4.0 (sqljdbc4.jar) is supported against SQL 2014.
Any input would be appreciated.
Thanks
We are on the following:
Apps 9.0
TR 9.1.5.1
All Windows 2008 Servers
Weblogic 12.1.2
JDK 1.6
SQL 2008 R2
We would like to upgrade (swap) the database machine from Windows 2008 to Windows 2012 and SQL 2008 R2 to SQL 2014. This will be a hard cutover with the new machine retaining the old name.
The dilemma is, do I keep the same JDBC (sqljdbc4.jar) drivers and SQL Native Access Client 10? It appears that I should based on everything I have read, which I believe to be incomplete data.
It looks like SNAC 11 is not certified to work with SQL Server 2014. The new Microsoft ODBC Driver 11 is not certified on any OS below Windows 2008 R2. But I cannot find anything determining whether SNAC 10 is supported with SQL 2014. I cannot find anything to the contrary either. I suspect it would be fine since no new features in JDE are being introduced that would need to take advantage of any new functionality in SQL 2014. We already have FASTFIRSTROW disabled.
It does look like JDBC 4.0 (sqljdbc4.jar) is supported against SQL 2014.
Any input would be appreciated.
Thanks