Angel Saenz-Badillos

does not contain a definition for

angelsb — Sat, 24 Feb 2007 06:06:00 GMT

Have you heard about extension methods yet? If you have then you probably know exactly what the title of this blog means. I can see this becoming one of the most asked about exceptions in the coming release. At least until the dust settles. <Edit>...(read more)

Blogging about link Extensions

angelsb — Mon, 29 Jan 2007 20:45:00 GMT

There are not a lot of guidelines about blogging, the one that I like to adhere to is that I only blog about bits that you can go and play with. This ends up creating gaps in my blogging history as I move to new unpublished products. I have moved, oh...(read more)

JDBC V1.1 Distributed Transactions with Read Committed and Snapshot isolation.

angelsb — Wed, 30 Aug 2006 00:57:00 GMT

One of the biggest changes you may not have noticed in the v1.1 2005 JDBC driver is that we have changed the default isolation level for Distributed Transactions from Serializable to Read Committed. This is in line with other JDBC drivers like our 2000...(read more)

JDBC Snapshot isolation level

angelsb — Thu, 24 Aug 2006 23:43:00 GMT

I have gotten some questions about using Sql Server 2005 with the 2005 JDBC driver. There are unfortunately a lot of misconceptions in this area. Here are some notes to make this a little bit easier to understand. The first thing you need to understand...(read more)

JDBC 2005 v1.1 is now available.

angelsb — Wed, 23 Aug 2006 03:51:00 GMT

The v1.1 2005 JDBC driver is now available for download here: http://msdn.microsoft.com/data/ref/jdbc/ This is a release I am personally really proud of, and we could not have done it without you! Maybe it’s the fact that not that many...(read more)

JDBC June 2006 Community Tech Preview available.

angelsb — Mon, 26 Jun 2006 22:03:00 GMT

Announcing the June 2006 Community Tech Preview of the JDBC 2005 driver: http://www.microsoft.com/downloads/details.aspx?familyid=f914793a-6fb4-475f-9537-b8fcb776befd&displaylang=en This preview contains all the changes of CTP 1 including...(read more)

JDBC v1.1 CTP and the Product Feedback Center

angelsb — Fri, 21 Apr 2006 02:35:00 GMT

When you get down to it Customer feedback is what makes a project like this interesting and worthwhile. This is the first project I have worked in where the Product Feedback Center has made such an important difference and a BIG thank you to those of you that have taken the time to file bugs directly on the JDBC provider: http://lab.msdn.microsoft.com/productfeedback/default.aspx

I want to make sure that you understand that we take these bugs very seriously. We triage them daily and treat them as the highest priority bugs come release time. Here is a list of customer bugs that we have received since we shipped RTM.

All of these bugs have been fixed in our latest JDBC V1.1 CTP. you can download this CTP by contacting the JDBC project manager directly at shelbyg<at>Microsoft<dot>com.

Bug Details: Statement.execute() returns incorrect results for stored procedures

http://lab.msdn.microsoft.com/ProductFeedback/viewfeedback.aspx?feedbackid=dc43eb80-69b5-4137-8671-9f4e813ce259

Bug Details: JDBC 2005 GA Driver error when running a callablestatement on SQLServer 2000

http://lab.msdn.microsoft.com/ProductFeedback/viewFeedback.aspx?feedbackid=3fcf439d-79ed-44d9-bbbf-320e4ee25d89

Exception Message: “SQL Error: A server cursor is not allowed on a remote stored procedure or stored procedure with more than one SELECT statement. Use a default result set or client cursor”

Bug Details: JDBC Driver executeBatch does not work with INSERT statement

http://lab.msdn.microsoft.com/ProductFeedback/viewFeedback.aspx?feedbackid=e13a8009-7466-4803-ba19-6bfd4b5f8966

Exception Message: “java.sql.BatchUpdateException: com.microsoft.sqlserver.jdbc.SQLServerException: sp_cursoropen/sp_cursorprepare: The statement parameter can only be a single select or a single stored procedure.“

Bug Details: SQL2005 JDBC Driver bug with time zone handling **Available as a QFE**

http://lab.msdn.microsoft.com/ProductFeedback/viewFeedback.aspx?feedbackid=e73c8b79-53a6-4779-98f1-71c0043179eb

Additional customer issues addressed that have no associated external bugs:

Bug Detail: Using sendStringParametersAsUnicode does not work with XA transactions.

Exception Message: “java.sql.SQLException: Failed to create the XA control connection.”

JDBC v1.1 CTP Using Type 2 Integrated Security

angelsb — Sat, 15 Apr 2006 02:22:00 GMT

To use the Type 2 Integrated Security feature with the v1.1 CTP (if you don't have this already make sure to get it! see my previous blog) you only need to make sure that the Windows authentication DLL is visible to the application that is going to use it (This usually means it is in the same directory or in a directory specified in your Path). Then specify integratedSecurity in your connection string and you are done.

The Windows authentication DLL is located under:

\sqljdbc_1.1\enu\auth\x86\sqljdbc_auth.dll //for x86 client OS versions
\sqljdbc_1.1\enu\auth\x64\sqljdbc_auth.dll //for AMD 64 clients running Windows 2003 64bit OS

import java.sql.*;

public class test {
public static void main(String[] args) {
try {
   java.lang.Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver");
   Connection conn = java.sql.DriverManager.getConnection("jdbc:sqlserver://servername;integratedSecurity=true");
   System.out.println("Connected!");
   conn.close();

} catch (Exception ex) {
ex.printStackTrace();
}
}
}

JDBC V1.1 CTP Available

angelsb — Sat, 15 Apr 2006 02:00:00 GMT

I am proud to say that the first community preview release of the SQL Server 2005 JDBC v1.1 driver is now available.

This build includes Type-2 integrated authentication for Windows XP and Windows 2003 clients (windows 2000 client support to come in the next CTP). It also incorporates bug fixes from customer feedback of the v1.0 driver and a fair ammount of plumbing under the covers. We really want to get as much feedback on this as possible.

To get the v1.1 CTP1 please email the JDBC Project Manager directly at
shelbyg<at>microsoft<dot>com.

I have a bet going with him on the number of requests he will receive so don't let me down!

JDBC 2005 beta 2 getting started with SQLEXPRESS

angelsb — Fri, 21 Oct 2005 00:35:00 GMT

Sql Express is going to be a good match for the Sql Server 2005 JDBC provider, it is free, it is relatively easy to set up and deploy and it has all the power of Sql Server 2005 for low end applications.

There are a few things to keep in mind when using Sql Express with the JDBC driver:

·         You need to enable mixed mode security when you install the server so that you can connect using user name and password.
·         Make sure that the sqlbrowser is enabled. Sql Server configuration Manager ->SQL Server 2005 Services ->SQL Server Browser ->Start
·         The JDBC provider only works with the TCP/IP protocol which is disabled by default on Sql Express. You need to enable the TCP/IP Protocol from the SQL Server Configuration Manager that ships with SqlExpress and re-start the server. Look under SQL Server 2005 Network Configuration -> Protocols for SQLEXPRESS-> TCP/IP->Enable.

Once you have set up Sql Express accordingly you can connect like this:

import java.sql.*;

public class test{
public static void main(String[] args) {
    try{
       java.lang.Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver");
       Connection c = java.sql.DriverManager.getConnection("jdbc:sqlserver://localhost\\SQLEXPRESS;user=myuser;password=mypass;");
       System.out.println("Connected!");
    }catch(Exception ex){
       ex.printStackTrace();
    }
}
}

If you are interested enough in this driver to have read this far you may be interested in learning more about our Data Coercion story:
http://blogs.msdn.com/dataaccess/archive/2005/10/19/482792.aspx

Rambling out, the information in this blog is provided "AS IS" and confers no rights.