I use net.sourceforge.jtds.jdbc.Driver. Does it surport FetchSize?
Thank you.
-Original Message-
From: John Villar [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 19, 2004 5:26 AM
To: Tomcat Users List
Subject: Re: Is there a way to set the size of ResultSet from MS SQL
Serve r
I don't know exactly, because i haven't used that feature ever but
it could support it, judging from the level of maturity jTDS drivers have.
Daxin Zuo escribió:
I use net.sourceforge.jtds.jdbc.Driver. Does it surport FetchSize?
Thank you.
-Original Message-
From: John Villar
jTDS is the fastest driver for SQL Server. We use it for some heavy traffic and found
it faster than the MS driver.
Allistair Crossley
-Original Message-
From: Brad McEvoy [mailto:[EMAIL PROTECTED]
Sent: 20 August 2004 01:17
To: 'Tomcat Users List'
Subject: [OFF-TOPIC] RE: Is
An issue even more important that speed with jTDS is the fact that it is
100% Open Source Java Code, and that's something M$ wont let you have.
The implications of having Open Source Software can be read at the OSI
web site www.opensource.org and the fact that it's 100% Java implies
that your
Remember that caching performance behaves like the gauss bell, it has an
optimal point where the performance is top notch, but variating from
there begins to affect the performance. to keep it simple, too much
nor too little isn't good you have to have the *right* quantity of cache
Out
On Fri, Aug 20, 2004 at 09:29:02AM -0400, John Villar wrote:
: Something off topic, does anyone has wondered why M$ hasn't developed
: its server line for linux? i know the usual response They want you to
: buy W2K Server, but that would be superficial thinking
Do you mean its .NET
that's true i really like some of their products its a shame
that their blind effort to deny something like linux is only going to
leave them behind in the long run or not so long? 8-)
The MS app-dev product line has many hooks into the OS itself. That
would bring about several
However, that would work only if the driver you're using uses the
FetchSize as a hint for caching records. In JDBC caching is primarily
the responsability of the Driver.
Brad McEvoy escribió:
something like this should do the trick
...
PreparedStatement pstmt =
thats true, but now i think about it, why would anyone use the JDBC driver
to connect to SQL Server? The JDBC driver is the worst one i've used and the
MS native driver is probably the best.
Out of curiosity I profiled the difference setFetchSize makes. Set to 100 on
Oracle it improves the time
something like this should do the trick
...
PreparedStatement pstmt =
con.prepareStatement(sql,ResultSet.TYPE_FORWARD_ONLY,ResultSet.CONCUR_READ_O
NLY);
pstmt.setFetchSize(100);
ResultSet rs = pstmt.executeQuery();
...
-Original Message-
From: QM [mailto:[EMAIL PROTECTED]
Sent:
10 matches
Mail list logo
