I've decided to help out a charity with there web site and want to do the pages in JSP etc. hence the "free" aspect - they have SQL Server 7.0 already - so I'm going to link to this... I've searched about but can't seem to find a driver for free that works on Windows. The ones I have found either run on Linux, or from the M$ site only apply to SQL Server 2000 Can anyone offer that elusive URL? thanks in advance Marcus
I've never come across a driver for SQL Server 7. (That's not saying that there isn't one, jsut that I havn't found it ) While you search, however, you can use the JdbcOdbcDriver. It provided for situations just like this.
Piscis Babelis est parvus, flavus, et hiridicus, et est probabiliter insolitissima raritas in toto mundo.
thanks Joel, getting myself a bit tied up there with the difference between Driver and Bridge etc. On finding the tutorial http://java.sun.com/docs/books/tutorial/jdbc/basics/connecting.html reckon it be relatively painless But it begs the question, how does this affect performance? This will be fine for my purposes I think, but had this been for a high transaction site - would there have been a benefit in say using the MS driver for SQL Server 2000 (and upgrading)? or moving to another platform, or even buying specific drivers from someone? [ May 16, 2003: Message edited by: Marcus Howarth ]
You will take a hit in performance, of course; adding the ODBC layer between the JDBC and the database creates another layer, and the more steps/layers in a process, the worse the performance. That being said, in a low-volume system I don't think that the hit in performance is going to be noticable. In a high-volume system, the hit would be noticeable, but only after you fine-tune your own code. (I use the JdbcOdbc driver all the time for my personal applications--ones that run only on my computer and against Access DBs. Any performance issues I see I attribute to Access and not to the Bridge driver). If you were workng on a high-volume system and needed that evera performance, I would recommend either buying the specific driver or updgrading to SQL Server 2000 (or Oracle, or whatever...)
You didn't say what platform the web app is running on... if it is non-Windows, then ODBC could be a headache. May I suggest a different tactic? Dump SQL Server and migrate to MySQL. Then you will have full access to their full blown Type 4 JDBC Driver, complete with DataSource and ConnectionPoolDataSource implementations. This is a no dollar-cost solution (there is of course, the cost of your donated labor, but this stuff is fun, right?). The biggest hurdle in this approach is moving away from stored procedures in the databse. If there aren't any, then you are pretty much home free. [ May 19, 2003: Message edited by: Philip Shanks ]
Philip Shanks, SCJP - Castro Valley, CA
My boss never outsources or has lay-offs, and He's always hiring. I work for Jesus! Prepare your resume!
Thanks Jon, I think that's the elusive url I was after - will try out, will be interesting too see what's going on there too in the source To answer your question Philip, obviously it's all fun but yes, all the Applications are running on windows so the odbc-bridge is working a treat with no hassles so far. I originally wanted to stick with SQL Server beacuse: a) I know it well, and it's faster to set up b) it's easy to integrate with the Access database's etc in that office, and c) simple data migration for my purposes but once that's done I take your point and will be going the [no dollar] mySQL route for future apps cheers Marcus http://jstuff.org