We are pleased to announce availability of the Microsoft JDBC 4.2 Driver for SQL Server! The updated driver provides robust data access to Microsoft SQL Server and Microsoft Azure SQL Database for Java-based applications.
JDBC and AIX 4.2.1 3004 Jun 15, 1999 6:22 AM ( in response to 3004 ) -- After I downloaded JDBC 734 for Solaries, I am getting this message, can someone tell me how to use JDBC connecting to Oracle 7.3.4 on AIX? Jul 01, 2015 The JDBC Driver for SQL Server is a Java Database Connectivity (JDBC) type 4 driver that implements full compliance with the JDBC specifications 4.1 and 4.2 and supports Java Development Kit (JDK) version 1.8.
The JDBC Driver for SQL Server is a Java Database Connectivity (JDBC) type 4 driver that implements full compliance with the JDBC specifications 4.1 and 4.2 and supports Java Development Kit (JDK) version 1.8. It supports the Transport Layer Security (TLS) 1.2 protocol for additional security over the internet. The JDBC 4.2 Driver for SQL also supports SQL Server’s AlwaysOn feature for High Availability and Disaster Recovery.
There are several additional enhancements available with the driver:
- The updated XA Transaction feature includes new timeout options for automatic rollback of unprepared transactions.
- New SQLServerBulkCopy class enables developers to quickly copy large amounts of data into tables or views in SQL Server and Azure SQL Database databases from other databases. For more details about what is currently supported in the bulk copy feature, please refer to What’s New in the JDBC driver.
The JDBC driver is part of SQL Server and the Microsoft Data Platform’s wider interoperability program, with drivers for PHP 5.6, Node.js, JDBC, ODBC and ADO.NET already available.
You can download the JDBC 4.2 driver here. We invite you to explore the latest the Microsoft Data Platform has to offer via a trial of Microsoft Azure SQL Database or by trying the new SQL Server 2016 CTP. Have questions?
Join the discussion on Stack Overflow. Running into an issue or have a suggestion? Let us know.
In my project, I having spring-jdbc:4.1.4.RELEASE which is working fine with no issues. Now for a new change I am trying to add spring-security-taglibs:4.0.4.RELEASE in my project, which is trying to download spring-security-taglibs:4.0.4.RELEASE and spring-jdbc-4.2.5.RELEASE, which will cause severe issue in my project. Because what spring-jdbc version required for me is 4.1.4.RELEASE which I specified explicitly. How can I avoid this? What is happening behind?
This is weird behavior from gradle
Suganthan Madhavan Pillai1 Answer
It seems that you have something like this in your build.gradle:
So this introduces a conflict in your dependencies which is visible in the output of the following task:
The arrow above (->) means that gradle default resolution strategy was used and 4.2.5 (newest) was chosen by gradle. You can read in gradle docs:
Gradle offers the following conflict resolution strategies:
Newest: The newest version of the dependency is used. This is Gradle's default strategy, and is often an appropriate choice as long as versions are backwards-compatible.
Fail: A version conflict results in a build failure. This strategy requires all version conflicts to be resolved explicitly in the build script.
What I see as options for you:
- use the newest
spring-jdbc(the best IMO) - use older spring security taglibs which dependes on older
spring-jdbc - resolve the version conflict within your scripts (the worst IMO) and keep your fingers crossed. You will need at least some luck :-) Details - here
Jdbc Driver Download
