Try http://www.inetsoftware.de/
I've used their driver before, and it worked quite well. Depending on your
needs, the price isn't too bad.
Good hunting,
Clayton Peirens
-----Original Message-----
From: Tomcat [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 20, 2001 11:57 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: JDBC Driver
In that case....if free implementations are not good enough....can you all
please suggest us a good commercial JDBC driver to connect to MS SQL 7,
which would be worth its money.
We are currently using Jrun 2.3.3 as a plugin to IIS4 on our NT4 box to
serve Servlets and JSP for our Virtual host customers...There are a lot of
problems associated with this. I was wondering if this is because we are
using ODBC system DSN to connect to SQL7.
1. High CPU utilization. (Jrun service needs to be restarted)
2. If sevlets are changed , the changes dont get effected in Jrun.
3. JSP sessions do not work.
Would shifting to Tomcat solve these problems or just using a type IV JDBC
driver to connect to database is sufficient.
Please let us know your experiences.
Best Regards
Sumith Ail
> >
> > Try FreeTDS (www.freetds.org, I think). I've used their straight TDS
> > driver with excellent results. They also have a Type 4 JDBC
> > driver as
> > well. I haven't had occasion to use it, but if it performs as well as
> > the straight TDS driver, I'm sure you'll be pleased.
> Unfortunately it looks like their straight TDS driver and the JDBC TDS
driver are developed by two separate teams. The JDBC driver
> is ok for queries and simple updates but from what I recall their idea
about what is a connection and when to automatically close
> connections and commit transactions was quite non-standard.
>
> I'd provide more detail but it was almost a year ago that I used it (and
the code to break it is on another machine). If you try it
> I think the following will show the problem:
>
> Get a connection:
>
> Call conn.setAutoCommit(false);
>
> get a prepared statement and update the database
>
> close the statement
>
> get another prepared statement and update the database
>
> close the statement
>
> commit the transaction
>
> close the connection.
>
> I think I remember their driver will either throw an exception somewhere
along the way or not show one of the updates.
>
> HTH
>
>
