Re: SQL Server 2000 database connection problems: Can ANY one help?

nkistrup_at_comcast.net
Date: 11/26/03


Date: Wed, 26 Nov 2003 10:57:12 -0500

THANKS Pete,

I figured out what the problem was (or could have been): A) Upgraded Eclipse
to version 2.1.2 (from 2.0), B) Created a user acct. for the database that I
was connecting to. This was a case of RTFM: Reading an ad for one of the
other JDBC drivers for SQL Server, Microsoft's driver does NOT support
Windows authentication . . . that's what I was doing.

Now the fun begins; literally. To make my life easier, can you (or anyone
reading this thread), recommend a good JDBC book. I'm coming from a strong
ADO & SQL Server background, so I know the basics (connection, command,
recordset, etc., etc. objects).

Niels

"Pete Bennett" <pete_bennett@dsl.pipex.com> wrote in message
news:3fc4ad1b$0$24064$cc9e4d1f@news.dial.pipex.com...
>
> Have you considered using a different driver? There are some very good
> type 4 drivers out there, albeit with the usual type 4 performance
overhead.
> I have used the IBM branded ones with WebSphere very successfully in
> production from time to time.
>
> Pete Bennett
> Distributed Systems Professional Services.
> <nielskistrup@comcast.net> wrote in message
> news:iNKdnZ0TUa9WuiGiRVn-gw@comcast.com...
> > Environment: SQL Server 2000, Windows 2000, Eclipse, and Microsoft's SQL
> > Server 2000 driver for JDBC
> > Problem: Connection to any table in my SQL 2000 database hangs. If I
stop
> > it, it produces the following exception:
> > com.sun.jdi.VMDisconnectedException: Got IOException from Virtual
Machine
> > at
> >
>
org.eclipse.jdi.internal.connect.PacketReceiveManager.getReply(PacketReceive
> > Manager.java(Compiled Code))
> >
> > at
> >
>
org.eclipse.jdi.internal.connect.PacketReceiveManager.getReply(PacketReceive
> > Manager.java:137)
> >
> > at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:168)
> >
> > at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:186)
> >
> > at
> >
>
org.eclipse.jdi.internal.ObjectReferenceImpl.invokeMethod(ObjectReferenceImp
> > l.java:350)
> >
> > at
> >
>
org.eclipse.jdt.internal.debug.core.model.JDIThread.invokeMethod(JDIThread.j
> > ava:647)
> >
> > at
> >
>
org.eclipse.jdt.internal.debug.core.model.JDIObjectValue.sendMessage(JDIObje
> > ctValue.java:67)
> >
> > at
> >
>
org.eclipse.jdt.internal.debug.eval.LocalEvaluationEngine.run(LocalEvaluatio
> > nEngine.java:231)
> >
> > at
> >
>
org.eclipse.jdt.internal.debug.core.model.JDIThread.runEvaluation(JDIThread.
> > java:562)
> >
> > at
> >
>
org.eclipse.jdt.internal.debug.eval.LocalEvaluationEngine.acceptClassFiles(L
> > ocalEvaluationEngine.java:218)
> >
> > at
> >
>
org.eclipse.jdt.internal.core.eval.RequestorWrapper.acceptClassFiles(Request
> > orWrapper.java:45)
> >
> > at
> >
>
org.eclipse.jdt.internal.eval.EvaluationContext.evaluate(EvaluationContext.j
> > ava:234)
> >
> > at
> >
>
org.eclipse.jdt.internal.eval.EvaluationContext.evaluate(EvaluationContext.j
> > ava:252)
> >
> > at
> >
>
org.eclipse.jdt.internal.core.eval.EvaluationContextWrapper.evaluateCodeSnip
> > pet(EvaluationContextWrapper.java:207)
> >
> > at
> >
>
org.eclipse.jdt.internal.debug.eval.LocalEvaluationEngine$1.run(LocalEvaluat
> > ionEngine.java:433)
> >
> > at java.lang.Thread.run(Thread.java:498)
> >
> > I have confirmed that server name is correct, and have pinged the port.
> > Looking at the following code snippet, what I am doing wrong?
> >
> > Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");
> > String url =
> >
"jdbc:microsoft:sqlserver://niels-bngjqb9y1:1433;DatabaseName=Forester;";
> >
> > Connection conn = null;
> >
> > conn = DriverManager.getConnection(url,"sa","");
> >
> >
> >
>
>



Relevant Pages

  • Re: XA and 2000 backwards compatibility
    ... As far as I can tell, the 2005 JDBC drivers do support XA on SQL Server ... I am going through the documentation for the SQL Server driver. ...
    (microsoft.public.sqlserver.jdbcdriver)
  • RE: [dbi] Re: MsSQL DBD::ODBC IsNull and undef
    ... I'd guess this is because the SQL Server ODBC driver is looking at your ... Martin J. Evans ... can you run your test script again but creating an OOB log file ...
    (perl.dbi.users)
  • Re: Padding using Type 4 Drivers
    ... |> value than what you have set in SQL Server 2000. ... |> settings that you require. ... |> Are you using the Microsoft JDBC driver or a third-party driver?. ...
    (microsoft.public.sqlserver.jdbcdriver)
  • Re: MsSQL DBD::ODBC IsNull and undef
    ... Martin J. Evans ... On 26-Jul-2005 Brian Becker wrote: ... > ensure you tell your driver the type of the column in bind_col. ... > I'd guess this is because the SQL Server ODBC driver is looking at your ...
    (perl.dbi.users)
  • Re: XA and 2000 backwards compatibility
    ... We haven't deployed the SQL2K XA driver either, so this should work for us. ... I am going through the documentation for the SQL Server driver. ... and enable XA transactions in MSDTC on the SQL Server ... Goto MSDTC tab on properties, click "Security Configuration" button, ...
    (microsoft.public.sqlserver.jdbcdriver)