I use the una driver from www.inetsoftware.de
They have a range of drivers, responsive tech support and decent prices.
I can't comment on your problems really. The failure to reload servlets may be
configuration related or NT related. One of my
clients uses ServletExec which sometimes reflects changes, sometimes reflects changes
after starting and stopping the IIS services
and sometimes requires a complete restart to reflect changes - go figure.
One way to have a bit of success with the JDBC-ODBC driver would be to access it from
a Connection Pool that has only a single
connection (ie max Connections = 1) . This should protect you from its lack of thread
safe operation and once you are ready to move
to a "real" jdbc driver you'll only need to change your configured driver.
BTW I have a wrapper for the bitmechanic connection pool that would allow you to do
this easily.
(http://www.knightsofthenet.com/projects/SQLPool) If anyone downloaded this before it
now compiles :-) and adds a shutdown hook for
worry free server operation.
HTH
> -----Original Message-----
> From: Tomcat [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, March 20, 2001 10: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
> >
> >
>
>
