Performance Problem, RPC Call auf SQLServer 2000

Question

Hi,
we have a performance problem with SQLServer 2000. We use Bea WLS 6.1, SQLServer
2000, and JDBC Driver mssqlserver4v65.jar from Bea.
we use this for performance optimization as in Documetation at
"http://www.datadirect-technologies.com/download/docs/jdbc/Jdbcref/jdbcdesign.html"
case 2
Stored Procedure can be optimized to use a server-side RPC. Because the application
calls the procedure by name and the argument values are already encoded, the load
on the database server is less
CallableStatement cstmt = conn.prepareCall ("Call getCustName (?)");
cstmt.setLong (1,12345);
ResultSet rs = cstmt.executeQuery();
But the checking in the SQlServer 2000 with SQL Profiler don't show the use of
RPC Call.
I can test the different from Query Analyser:
exec IF_GetBueroStatistik 1 -> SQLProfiler: SQL:BatchCompleted
{call IF_GetBueroStatistik(1)} -> SQlProfiler: RPC:Completed
But the Call from Bea Aplication make in SQlProfiler alwasy SQl:BatchCompleted.
The RPC ist faster from the Batch call.
is that a bug in the driver implementation?
can any help me with a solution or workaround?
thanks Halim

Answer 1

Hi,
thank you very much Joe.
Halim.
Joseph Weinstein <[email protected]> wrote:
>
>
Halim wrote:
Hi,
we have a performance problem with SQLServer 2000. We use Bea WLS 6.1,SQLServer
2000, and JDBC Driver mssqlserver4v65.jar from Bea.You shouldn't be using the 6.5 version of the driver anyway. The 7.0
version is better,
but what you are seeing is that our driver does send fresh SQL for PreparedStatements,
which is not as fast as using the RPC protocol. It's not a bug, but it
is a feature we didn't
implement.
You should probably download and use the free driver from MS. It does
implement
the procedure protocol.
Joe
we use this for performance optimization as in Documetation at
"http://www.datadirect-technologies.com/download/docs/jdbc/Jdbcref/jdbcdesign.html"
case 2
Stored Procedure can be optimized to use a server-side RPC. Becausethe application
calls the procedure by name and the argument values are already encoded,the load
on the database server is less
CallableStatement cstmt = conn.prepareCall ("Call getCustName (?)");
cstmt.setLong (1,12345);
ResultSet rs = cstmt.executeQuery();
But the checking in the SQlServer 2000 with SQL Profiler don't showthe use of
RPC Call.
I can test the different from Query Analyser:
exec IF_GetBueroStatistik 1 -> SQLProfiler: SQL:BatchCompleted
{call IF_GetBueroStatistik(1)} -> SQlProfiler: RPC:Completed
But the Call from Bea Aplication make in SQlProfiler alwasy SQl:BatchCompleted.
The RPC ist faster from the Batch call.
is that a bug in the driver implementation?
can any help me with a solution or workaround?
thanks Halim