- This topic has 12 replies, 5 voices, and was last updated 20 years, 3 months ago by
.
-
Posts
-
– System Setup ——————————-
Operating System and version: Windows XP SP1
Eclipse version: 3.0.0
Eclipse build id: 200406251208
Fresh Eclipse install (y/n): N
If not, was it upgraded to its current version using the update manager? No
Other installed external plugins:
Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*: 0
MyEclipse version: 3.7.200
Eclipse JDK version: 1.4.2_05
Application Server JDK version: 1.4.2_05
Are there any exceptions in the Eclipse log file? No
– Message Body ——————————-
I’m using the jTDS 0.8 driver, and when I try to connect to a MS SQL Server 2000 database, using URL “jdbc:jtds:sqlserver://portaldev.suzano.com.br/excelencia”, it freezes while “Reading Database Metadata” from “tempdb” (I think it’s a DB created by the SQL Server install).Both my application and DBVisualizer connect OK to this DB with this same URL.
Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*: 0
The problem might be your Eclipse installation. Please make sure you downloaded and installed the FULL Eclipse SDK. The easiest way to check from within Eclipse is to look at Help > About Eclipse Platform > Feature Details and check the features listed. For Eclipse itself you should see 7 features whose provider is Eclipse.org. If you see fewer than 7, the problem is caused by installing a “trimmed down” version of Eclipse that does not have all the infrastructure needed for MyEclipse. You’ll then need to uninstall and reinstall after downloaded the full Eclipse SDK, which is about 80MB in size.
dserodio –
Any luck with DB Explorer and SQLServer yet? I am the developer who worked on bringing DB Explorer to MyEclipse (started off its life as JFaceDBC and SQLExplorer). I have not found anything on the JFaceDBC forums/support lists to indicate there is a problem with SQLServer and the plugin. Do you get any error logs? or does eclipse just totally freeze? How big is the database we are talking about? The fact that it is looking at a database called ‘tempdb’ instead of the one you specified (‘excelencia’) might be a concern, but frankly i do not know anything about M$ SQLServer 😈 I will be happy to help in anyway I can.
jeff
MyEclipse SupportI take that back re: JFaceDBC. I did find one posting on the sf.net forums;
http://sourceforge.net/tracker/index.php?func=detail&aid=777027&group_id=56713&atid=481540
Says JFaceDBC has trouble with the BEA JDriver for MS SQL Server, but that is all, no follow up. Have you tried this driver as well?
jeff
MyEclipse SupportI had this exact same problem with JFaceDBC, but since it was not maintained anymore (at least for Eclipse 3), I didn’t bother submitting a bug report.
Where can I download the BEA drivers?
If this helps, here is an open source Type 4 JDBC driver for SQL Server as well: http://jtds.sourceforge.net/
Its a pretty active project.
That’s exactly the driver I tried. We use this driver in production, with DbVisualizer, and other Java tools with no problems. I’m currently using 0.8, the latest stable release.
It’s unlikely we will be able to resolve this soon. I have no access to a SQL Server database instance. We will try to address it, but the main drive now is to enhance the overall stability of the product. There just has not been as big a call for attention to SQL Server. I promise it won’t be ignored, but it will take a while.
Thanks for the feedback. You got some really nice Customer Support over there…
I don’t like MS SQL Server either, but it’s the customer’s choice… 😕I’m accessing our Ingres database using the database explorer, and the first few times I actually got the impression the application froze. It really doesn’t, it just takes a very, very, very long time to load the tables (many minutes). When I’m using JFaceDB with Eclipse 2.1 it loads in seconds (smae drive, same database). I know it is proportional to the to how many tables you have in your database. We have 300+ tables in our main database, but even loading a smaller database with 20 tables or so takes a least 10 seconds.
