-
I had nothing to do with the recent activity. :) Glad to see it's going again, though!
Dave.
2009-07-23 17:33:52 UTC in jTDS - SQL Server and Sybase JDBC driver
-
I don't think there's any other way to do what you want to do without a custom version.
Please create a new tracker item and post a patch of your changes to it.
Thanks!
Dave.
2009-06-04 22:58:47 UTC in jTDS - SQL Server and Sybase JDBC driver
-
Try using Microsoft's database tool to connect using the same information.
You can also try enabling verbose logging while connecting. (I think this requires setting a system property; it's been a while since I tried doing it. Try searching through the source code to find it.)
Dave.
2009-05-13 20:43:58 UTC in jTDS - SQL Server and Sybase JDBC driver
-
Try this URL instead:
jdbc:jtds:sqlserver://127.0.0.1:1433/a;user=Administrator;password=password
See this URL for more information:
http://jtds.sourceforge.net/faq.html#urlFormat
Dave.
2009-05-13 00:36:41 UTC in jTDS - SQL Server and Sybase JDBC driver
-
Please attach a patch if you have one. Thanks!
IIRC, I think exceptions are chained (in other parts of jTDS) based on the version of Java being used, or they're chained differently on older JDKs than newer ones. There should be examples of chained exceptions in other parts of the code.
Dave.
2009-04-21 13:10:10 UTC in jTDS - SQL Server and Sybase JDBC driver
-
Since jTDS isn't being actively developed, please file a tracker item so that this may be fixed in the future. I agree that this is something that will need to be addressed in jTDS going forward.
Thanks!
Dave.
2009-04-21 09:58:58 UTC in jTDS - SQL Server and Sybase JDBC driver
-
Which tracker ID is it?
It is possible that the fix was committed after the last release. You could try to check out the source from CVS and build jTDS yourself to see if it's fixed.
Dave.
2009-04-04 03:03:12 UTC in jTDS - SQL Server and Sybase JDBC driver
-
As far as I remember, "instance names" only worked locally. (Do they work "remotely" when you connect via the SQL Server database tool? If so, then this is a deficiency/bug in jTDS. Please file a bug about it on the tracker.)
I believe jTDS ignores any properties that it doesn't know about, so adding "instanceName=mssqlserver" is the same as removing...
2009-03-19 20:11:39 UTC in jTDS - SQL Server and Sybase JDBC driver
-
Yes, add a property to the connection URL called "instance", e.g., "instance=YourInstanceName".
See this page for more details:
http://jtds.sourceforge.net/faq.html#urlFormat
Dave.
2009-03-19 15:35:46 UTC in jTDS - SQL Server and Sybase JDBC driver
-
With namedPipe=true set and running on Windows, jTDS tries to open the "file" (the named pipe) at a special path, but I think it needs a database name to work properly.
Try adding a database name to your URL to see if that fixes the issue:
jdbc:jtds:sqlserver://1.1.1.1:1433/databasename;namedPipe=true
Dave.
2009-03-02 14:18:56 UTC in jTDS - SQL Server and Sybase JDBC driver
