FIX: SQL Server 2000 Driver for JDBC leaks server cursors (820773)

MORE INFORMATION

Steps to reproduce the problem

1. Start SQL Profiler to trace the calls to the SQL Server that the application connects to. Make sure that the trace properties are set to include the Stored Procedures event. Start the trace.
2. Compile, and then run the following Java code.
   
   Note You must replace the server name, the user id, and the password in the connection string as appropriate for your environment.

   import java.sql.*;
   import java.io.*;
   import java.lang.Object.*;
   
   public class CursorLeak
   { 
   
   	
   	public static void main( String args[] )
   	{ 
   	
   		Connection conn = null; 
   		Statement stmt = null; 
   		ResultSet result = null; 
   
   		try
   		{
    
   			Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");
   			conn=DriverManager.getConnection("jdbc:microsoft:sqlserver://myServer:1433;DatabaseName=myDatabase;SelectMethod=Cursor;User=UserID;Password=password" );
   			
   		      //Workaround #1: Use SelectMethod = Direct
   		      //conn=DriverManager.getConnection("jdbc:microsoft:sqlserver://myServer:1433;DatabaseName=myDatabase;SelectMethod=Direct;User=UserID;Password=password" );
   		}
   		catch( Exception e )
   		{ 
   			System.out.println( e ); 
   		} 
   
   		try
   		{ 
   			stmt = conn.createStatement(); 
   			String query = "Select CompanyName, City, Phone from Customers"; 
   			stmt.execute( query ); 
   		      
   		      //Workaround #2: If you call executeQuery() instead of execute(), stmt.close() closes the cursor.
   		      //ResultSet rs = stmt.executeQuery( query );	
   		
   		      //Workaround #3: If you call getResultset() after you call execute(), stmt.close() closes the cursor.
   		      //ResultSet rs = stmt.getResultSet(); 		
   			
     		      //Closing explicitly the ResultSet closes the cursor
   		      //if(stmt != null)
   		      	//rs.close();
   
   			System.out.println( "Close" ); 
   			
   		      	stmt.close();
   
   			try
     			{
   				System.out.println("Wait");
   				Thread.sleep(10000);
   			}
   			catch(Exception e)
   			{
   				System.out.println(e.getMessage());
   			}  
   		}
   		catch( SQLException e )
   		{ 
   				System.out.println( e ); 
   		}
   	}
   }

3. Check the Profiler output. You see sp_cursoropen and sp_cursorfetch. However, but the sp_cursorclose call is not there.