PreparedStatement with a mssqlserver4v65 DataSource

Question

We have been trying to boost our performance by using PreparedStatement
with the WLS MSSQL Driver, but gained none. Are any of you out there
using PreparedStatements with that driver and noticing performance
improvement?
On a related note, what could we possibly do so wrong with that driver
that would annihilate the performance boost we should have gained? If we
switch to another driver with the exact same code, we see that we gain a
noticable performance gain thanks to the use of PreparedStatements.
Any idea?
Thanks,
Christophe

Answer 1

Thanks for your active feedback, Slava. Joe explained everything in
another email in this thread.
And Joe, since you seem to read every post, a BIG THANKS to you too!
Christophe
Slava Imeshev wrote:
Christophe,
First, you have to close result set explicitly.
Second, you say you don't see performance gain.
What did you use to compare performance of prepared
statement?
Regards,
Slava Imeshev
"Christophe Warland" <christophe.warland_REM@OVE_s1.com> wrote in message
news:3C60270F.4060900@OVE_s1.com...
We are using WLS 6.1 SP1.
Our code is actually part of a huge piece of our architecture, so I can
not easily give something to you that would compile on your machine. But
it would look like the following excerpt. 'runTest' acquires a
connection from a JNDI DataSource, creates a PreparedStatement and then
loops on 'testItSingle'.
public long runTest() throws Exception {
long start = System.currentTimeMillis();
// acquire connection from JNDI datasource
// (not shown here)
Connection con = getConnection();
String sql = getSql();
PreparedStatement st = con.prepareStatement(sql);
for (int i = 0; i < TEST_LEN; ++i) {
testItSingle(i, st);
close(st);
close(con);
long end = System.currentTimeMillis();
return end - start;
protected void testItSingle(int i, PreparedStatement st)
throws Exception {
String[] elem = DATA;
String p1 = elem[0]; // acct id
String p3 = elem[1]; // prod code
st.setString(1, p1);
st.setLong(2, ISOCode);
st.setString(3, p3);
ResultSet rs = st.executeQuery();
protected String getSql() {
return "SELECT A.versionStamp AS aLockValue, B.versionStamp AS
bLockValue, A.VFMAcctKy, A.SECEntityKy, A.VFMProductKy, A.acctID,
A.ISOCurrencyCdKy, A.isSrcXferEnabled, A.isDestXferEnabled,
A.maxXferAmt, A.minXferAmt, A.maxPmtAmt, A.minPmtAmt, A.versionStamp,
ledgerBal, ledgerBalDttm, availBal, availBalDttm, overdraftBal,
overdraftBalDttm, ytdInt, ytdIntDttm, lstYrInt, lstYrIntDttm, sumField1,
sumField2, sumField3, sumField4, sumField5, sumField6, sumField7,
sumField8, sumField9, sumField10, sumField11, sumField12, sumField13,
sumField14, sumField15, sumField16, sumField17, sumField18, sumField19,
sumField20 , E.VFMProdSubTypeKy, null VFMCustomerKy FROM VFMAcct A,
VBMDepositAcct B, VFMProduct E WHERE A.VFMAcctKy = B.VFMAcctKy AND
E.VFMProductKy = A.VFMProductKy AND A.acctID = ? AND A.ISOCurrencyCdKy =
? AND E.productCode = ? ORDER BY E.VFMProdSubTypeKy";
We also try to close statement and result set inside 'testItSingle' but
it didn't imporve anything. The preparedstament was actually reopened
silently and running just fine.
Thanks for your help,
Christophe
Slava Imeshev wrote:
Christophe,
Which version of weblogic and service pack do you use?
Could you show us your questionable code?