rolling back transactions with MS SQL Server?

I'm unable to roll back transactions using MS SQL Server. I'm
connecting to the database with the following parameters:

jdbc:microsoft:sqlserver://
GX520-4HSMFC1:1433;databaseName=RECON;SelectMethod=cursor

The code that creates the connection is:
connection = connManager.get(Thread.currentThread().getName());

if(connection == null){
connection = createNewConnection();
connection.setAutoCommit(false);
}

When a connection is created and records are written, the following
statement fails to rollback the new records:
connection.rollback();

I have a feeling the problem lies in the SelectMethod=cursor setting.

Is there a way around this or am I missing something?

.

Relevant Pages

  • Re: My Book is Incomplete Regarding SQL Commands ;-(
    ... Hitchhiker's Guide to Visual Studio and SQL Server ... Create a Connection object and pass in a ConnectionString to ... manage the database table you reference. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: (Newbie)Application Roles
    ... level: the database itself. ... SQL Server accommodates these needs through the use of application ... the user's connection through a specific application. ... the connection permanently loses all permissions applied to ...
    (microsoft.public.sqlserver.security)
  • Re: Help! Set up Windows Group to access application
    ... The connection string for a trusted connection is: ... --add login as database user ... SQL Server MVP ... If you have troubles with finding your ways in Crystal Reports, ...
    (microsoft.public.sqlserver.security)
  • Re: My Book is Incomplete Regarding SQL Commands ;-(
    ... Visual Studio but not to VS 2003. ... Create a Connection object and pass in a ConnectionString to address ... manage the database table you reference. ... Yep, my latest book can help too, but mostly if you're targeting SQL Server ...
    (microsoft.public.dotnet.framework.adonet)
  • RE: Logging in in background
    ... wold take all kinds of modifictions as I'd need to be checking that each SQL ... my database and all have connection strings associated with them. ... I suspect that there is also an issue on the SQL Server side as I keep ...
    (microsoft.public.access.modulesdaovba)