Re: JDBC for sql server: delays experienced when using Connection.prepareCall()
From: Anthony (anthony_at_jayasekera.net)
Date: 14 May 2004 01:46:39 -0700
Thanks greatly Joe. The selectMethod=cursor property setting solved
my prepareCall problems. I am still getting the delay on creating the
connection but this is a hit I am willing to accept. I am only
actively loading one jdbc driver so unless some others are loaded by
default this shouldn't be the cause of the problem. It is probably a
network issue of the type you describe.
To everyone else out there, I'd just like to say that Joe replyed to
this posting within a couple of hours. Pretty danm good considering
the issue has nothing directly to do with a BEA product.
Joe Weinstein <joeNOSPAM@bea.com> wrote in message news:<40A24E79.email@example.com>...
> Hi. Two things:
> What MS jdbc driver are you using? If it's MS's free type-4 driver
> try adding the property selectMethod=cursor. That should help with
> the delay with subsequent statements.
> Also, how many drivers are registered with DriverManager? DriverManager
> has to blindly pass your URL and properties to every driver it knows
> about till it finds one that doesn't throw an exception and returns a
> connection. This could take some time with lots of drivers.
> However, it sounds like a DNS lookup problem with the DBMS machine
> name you're giving in the URL.
> Joe Weinstein at BEA