June 2, 2008 at 12:00 am
Hi,
I am using IBM websphere 6.1.0.9 and sql server 2005.
I have a doubt on this websphere and sql server 2005 connectivity.
If i run the query in the mgmt studio it is giving result in 2 seconds, but if i run the same query through webspher 6.1.0.9 app server it is taking 5 seconds to get the results.
Is there any compatiable problem with websphere appserver 6.1.0.9 with sql server 2005. We are using connectdirect jdbc driver which is a built-in inside the websphere 6.1.
What could be the problem??
June 2, 2008 at 5:55 am
It is most likely some application-level overhead in building a recordset. The best way to determine where the problem resides is to use profiler to trace the activity on the SQL server. You can track when the command is sent to the SQL Server, if it is the command you expect, how long the command takes to run, etc.
June 2, 2008 at 6:11 am
Hi,
I have used sql profiler also to find out the problem..
In sql profiler what i found that it was using sp_cursorprepare to supply all the parameterized values,because we are using preparedstatement in the code.
After 5 seconds it called sp_cursorunprepare and then sp_cursorclose...
I dont know whether the problem is caused by app server or jdbc driver (IBM WebSphere Connect JDBC driver for MS SQL Server).
should i need to increase the memory to run the select query if it comes from app server?
June 2, 2008 at 6:49 am
I'd work on making adjustments to the code or the application server so that it doesn't make these types of calls. They shouldn't be required and there's probably a way around them. I'm not familiar with the particular drivers you're using, but other drivers I've used, up to & including nHibernate, don't require those types of calls to process preprared statements.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply