Microsoft JDBC Driver


DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 4 of 4

Thread: Microsoft JDBC Driver

  1. #1
    Colin Guest

    Microsoft JDBC Driver


    I tested this driver a few weeks ago and it was 3X slower with our software
    than any other MS SQL Driver.

    It also had a major flaw with JDBC escape syntax (which is important if you
    are writing cross DB SQL!)

    I would also like to point out, call me paranoid if you so wish, but .NET
    is in competition with J2EE and JDBC is a fundamental component of J2EE so
    don't expect fantastic code in Microsoft's equivalent driver...and after
    all the damage they have tried to do against JAVA in the past I will not
    be using it any code from them since I could not trust, yes trust, the code
    to not have some fundamental quirk somewhere??

    The only good thing it had going was that it was free! JSQLConnect is probably
    the best out there.

  2. #2
    Elias Morales Guest

    Re: Microsoft JDBC Driver


    First, I apoligyze for my English (my first language is spanish Mexico)

    I want to add.

    I also tested this driver and it throw me the exception:

    'java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Can't
    start a cloned connection while in manual transaction mode.'

    If a try the same query with the i-net Opta Driver I can do it.



    "Colin" <java.@127.0.0.1> wrote:
    >
    >I tested this driver a few weeks ago and it was 3X slower with our software
    >than any other MS SQL Driver.
    >
    >It also had a major flaw with JDBC escape syntax (which is important if

    you
    >are writing cross DB SQL!)
    >
    >I would also like to point out, call me paranoid if you so wish, but .NET
    >is in competition with J2EE and JDBC is a fundamental component of J2EE

    so
    >don't expect fantastic code in Microsoft's equivalent driver...and after
    >all the damage they have tried to do against JAVA in the past I will not
    >be using it any code from them since I could not trust, yes trust, the code
    >to not have some fundamental quirk somewhere??
    >
    >The only good thing it had going was that it was free! JSQLConnect is probably
    >the best out there.



  3. #3
    Ray Clough Guest

    Re: Microsoft JDBC Driver


    "Elias Morales" <alejandromt@hotmail.com> wrote:
    >
    >First, I apoligyze for my English (my first language is spanish Mexico)


    >
    >I want to add.
    >
    >I also tested this driver and it throw me the exception:
    >
    >'java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Can't
    >start a cloned connection while in manual transaction mode.'
    >
    >If a try the same query with the i-net Opta Driver I can do it.
    >
    >
    >
    >"Colin" <java.@127.0.0.1> wrote:

















    >>
    >>I tested this driver a few weeks ago and it was 3X slower with our software
    >>than any other MS SQL Driver.
    >>
    >>It also had a major flaw with JDBC escape syntax (which is important if

    >you
    >>are writing cross DB SQL!)
    >>
    >>I would also like to point out, call me paranoid if you so wish, but .NET
    >>is in competition with J2EE and JDBC is a fundamental component of J2EE

    >so
    >>don't expect fantastic code in Microsoft's equivalent driver...and after
    >>all the damage they have tried to do against JAVA in the past I will not
    >>be using it any code from them since I could not trust, yes trust, the

    code
    >>to not have some fundamental quirk somewhere??
    >>
    >>The only good thing it had going was that it was free! JSQLConnect is probably
    >>the best out there.

    >


    I also have some problems with this driver. I just got my computer "upgraded"
    to Win XP. Ever since this, I've gotten sporadic problems with code which
    worked perfectly when my server had NT4.0. I can have two structurally identical
    tables, and one will throw exceptions, typically "can't translate to the
    required data type" type of error. The other table will read perfectly.
    The definitions of the tables is identical (they were created by the same
    program). Also, I'm having trouble creating reliable connections - some
    user accounts will not allow login, although they did fine under NT4.0.
    I've read reports where the MS JDBC driver was close to the fastest, but
    I've got an app that I do not believe does anything stupid, but is incredibly
    slow.

    I do trust Microsoft. I trust them to sabotage Java whenever possible.
    I would not put it past them to limit the ability of users of SQL Server
    to use Java, even if it seems to make sense for them to broaden the use of
    SQL Server in the Java community. It could be argued that they derive benefit
    by forcing developers onto .NET by having crappy JDBC performance.
    - Ray Clough

  4. #4
    Madock Guest

    Re: Microsoft JDBC Driver


    Try to add a "SelectMethod" parameter in connection string and set it to
    "SelectMethod=Cursor" default is "SelectMethod=Direct".


    "Elias Morales" <alejandromt@hotmail.com> wrote:
    >
    >First, I apoligyze for my English (my first language is spanish Mexico)


    >
    >I want to add.
    >
    >I also tested this driver and it throw me the exception:
    >
    >'java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Can't
    >start a cloned connection while in manual transaction mode.'
    >
    >If a try the same query with the i-net Opta Driver I can do it.
    >
    >
    >
    >"Colin" <java.@127.0.0.1> wrote:
    >>
    >>I tested this driver a few weeks ago and it was 3X slower with our software
    >>than any other MS SQL Driver.
    >>
    >>It also had a major flaw with JDBC escape syntax (which is important if

    >you
    >>are writing cross DB SQL!)
    >>
    >>I would also like to point out, call me paranoid if you so wish, but .NET
    >>is in competition with J2EE and JDBC is a fundamental component of J2EE

    >so
    >>don't expect fantastic code in Microsoft's equivalent driver...and after
    >>all the damage they have tried to do against JAVA in the past I will not
    >>be using it any code from them since I could not trust, yes trust, the

    code
    >>to not have some fundamental quirk somewhere??
    >>
    >>The only good thing it had going was that it was free! JSQLConnect is probably
    >>the best out there.

    >



Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center