Compartilhar via

Microsoft JDBC 4.0 Driver for SQL Server CTP is Released!!!!

  • Artigo

Dear SQL Server developers and users:

As a follow up to my last post regarding the next release of our JDBC driver called the Microsoft JDBC Driver 4.0 for SQL Server, I am very pleased to announce the availability of our first community technology preview (CTP).

https://www.microsoft.com/downloads/details.aspx?FamilyID=49c554ca-41a0-472c-b728-75df5789369c

This release includes:

- Type-4 Kerberos Integrated Security

o Support for authentication via TGT in cache

o Login configuration file support

- Client side support for SQL Server AlwaysOn Feature for Denali

o Support for multi-subnet failover for AlwaysOn

Let us know how we’re doing and give us your feedback through the Microsoft SQL Server Data Access Forum, Microsoft Connect, or this blog.

 

Thank you,

Amina Saify, Program Manager – SQL Server/JDBC

Comments

  • Anonymous
    January 25, 2011
    Thanks for the update. Almost a year ago I posted the following comment: "could you please consider a better implementation for PreparedStatement.setQueryTimeOut(). Each time a statement is executed, a new Thread is created (SQLServerStatement.StmtExecCmd.startResponse()), likely causing many thousands of threads to be created when an application is running. Appearently, garbage collecting has a hard time collecting these threads causing a performance bottle neck (not to say major debugging issues). This is also mentioned in: forums.sun.com/thread.jspa Has this been addressed? If so, this is a major issue for us and would definitely be a reason to start testing and using this release. kind regards, Christiaan

  • Anonymous
    February 01, 2011
    Hi, I have been using SQL Server 2008 R2 for last 6 months. It seems the call to JDBC function getSchema/listSchema does not return the schema names and still refers to user names/roles. While using a JDBC tool to access the database I do not get to see a schemas, if I do not have a user of corresponding name. I think SQL Server 2005 onwards MIcrosoft's SQL Server dev team has disintegrated the coupling between Schema and user, the same needs to be done for JDBC as well. Thanks and Regards Sameer Kumar Database Administrator Misys Banking Services

  • Anonymous
    February 08, 2011
    The comment has been removed

  • Anonymous
    March 25, 2011
    How about passing TVP to SQL stored procs from Java? Did that make this release?

  • Anonymous
    April 07, 2011
    Sorry TVP did not make it in this this release.

  • Anonymous
    May 09, 2011
    Does "Type-4 Kerberos Integrated Security" translate to Type-4 support on non-windows clients ? Meaning a non-windows client can use Type-4 Integrated Security , ie windows authentication ..  ? The current MS driver does not support this so it has only limited Type-4 support.

  • Anonymous
    May 13, 2011
    The comment has been removed

  • Anonymous
    June 01, 2011
    I have tried with the latest jdbc and jdbc 3.0 as well and the issue with schema listing still persists. :( Also, I am facing an issue with decimal string formatting. It seems you guys have implemented math.bigDecimal.toString() while implementing inputString interface for readDecimal method. This gives an issue whenever I try to fetch decimal column of precision greater than 6. I get a value 4E-7 etc. Can you provide a connection property to choose between toString() or toPlainString() [which would have shown me 0.0000004 instead of 4E-7]? IBM has done that recently in DB2 LUW release 9.7. Or if you can use toPlainString() in general instead of toString()? I guess Oracle does that only. I hope to see a positive response on both the issues and also on the issue I had posted previously. Thanks and Regards Sameer Kumar

  • Anonymous
    June 09, 2011
    The comment has been removed

  • Anonymous
    July 28, 2011
    I have long been a supporter of SQL Server as an excellent choice for most enterprise software database requirements. But Microsoft's consistent treatment of Java developers as second class systems has made this increasingly difficult. Whether it's egregious bugs, poor performance (e.g. the new-thread-per-timeout-call issue), or just lagging for years behind the curve (e.g. TVPs), the performance here is so disappointing I just cannot stand behind you guys anymore. I hope this situation improves in the near future.

  • Anonymous
    July 28, 2011
    @Daveg, thank you for your feedback. Trust me when I say we are not treating Java developers as second class systems. We are heavily investing in our JDBC driver. Both query timeout and TVP have been on our books and we have plans to address them as soon as we can. What other performance issues have you seen with your driver? @Nivedittan, are you running your application on Windows Azure and connecting to SQL Azure or your application is running locally and connecting to SQL Azure? @Jeff, yes JDBC 4.0 type-4 integrated security feature is supported on non-windows clients as well. @ Sameer, I will follow up on these two issues you posted. if you want to get faster response, you can post these issues on our forum. Product team and support team regularly monitor our forums for any JDBC related issues. social.technet.microsoft.com/.../threads Thanks Amina

  • Anonymous
    August 24, 2011
    The comment has been removed