Link to home
Start Free TrialLog in
Avatar of Axter
AxterFlag for United States of America

asked on

Free JDBC-ODBC Bridge drivers

Are there any free JDBC-ODBC Bridge  drivers that will work with MSSql Server, and if so, can someone give me a good download link?
Avatar of bloodredsun
bloodredsun
Flag of Australia image

The JDBC-ODBC bridge driver from Sun is included with the Java 2 SDK Standard Edition as package sun.jdbc.odbc.
Avatar of Axter

ASKER

>>The JDBC-ODBC bridge driver from Sun is included with the Java 2 SDK Standard Edition as package sun.jdbc.odbc.

How do you connect to this driver?
>.How do you connect to this driver?

Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Just like above!!
Avatar of Axter

ASKER

>>Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");

How do I connect to the driver using NetBeans GUI?
Avatar of Axter

ASKER

I'm still having problems.

When I try to make a connection, I get a "Unable to add connection prompt"
See following screen shot:
http://axter.com/tmp/jdbcproblem.jpg

I downloaded the driver from the MS site to see if that help any, but I still can't make a connection.
Avatar of Axter

ASKER

zloy_ochen,
The link you posted is for a trial version.  I'm not looking for a trial version.
I'm looking for a free driver that will work with MSSQL server.

I've already downloaded the driver from MS, and I haven't been able to get that one to work.
What about the port number and database name? And is that doesn't help, change the url to an IP number.
SOLUTION
Avatar of CEHJ
CEHJ
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Axter

ASKER

Well that was a really stupid mistake!!!

I was too busy looking at it as a Java problem instead of seeing it as a really simple ODBC problem.


Thanks
8-)
Your best solution for Microsoft SQL Server is to not use ODBC at all.  There is an EXCELLENT free, open source Type 4 (no native code!) JDBC driver called JTDS.  Google for JTDS (it is a SourceForge project) and you'll be absolutely impressed with the performance and reliability.
Avatar of Axter

ASKER

>>There is an EXCELLENT free, open source Type 4 (no native code!) JDBC driver called JTDS.  Google for JTDS (it is a SourceForge project)
>>and you'll be absolutely impressed with the performance and reliability.

How much of a performance difference are we talking about?
Substantial performance benefits (it uses a wire level protocol), plus you need zero MSSQL stuff on the box.  No network client DLL's, etc..  Almost no way to crash your server using it, whereas with the JDBC/ODBC bridge, crashing is a common occurrence.  The only reason you wouldn't use it is if, for some reason, the SQL administrator wouldn't allow MSSQL to listen on TCP/IP and required named pipes only.  Otherwise, use the pure Java, Type 4 JDBC driver, always!
Avatar of Axter

ASKER

>>Substantial performance benefits (it uses a wire level protocol), plus you need zero MSSQL stuff on the box.

Are we talking about 5%, 10%, 20%, 50%, 100%, 1000% ????

I'm just looking for a ball park figure.
And have you tested this, or are you getting the stats from somewhere else, and if so, can you give me the links.