Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2003-10-29 : 08:22:27
|
Bhupesh writes "I was running traces on our SQL Server for checking the performance of a particular Stored Procedure. I am executing the Stored procedure in query analyzer and running traces to see how well the stored procedure is performing. Following is what I see in SQL ProfilerEventClass CPU Reads Writes DurationSP:Completed 125 SQL:StmtCompleted 31562 68636 0 31672 My SQL Statement is an EXECUTE STATEMENT executing the Stored Procedure. What I do not understand is if the SP itself executes in 125 ms, why does SQL statement take 31.672 sec to execute.There are no other SQL Statements other than the execute statement. To me it looks like the Stored procedure itself gets executed, but for some reason SQL Server is taking a long time to return the information. Has someone else faced similar performance problems in SQL Server 2000." |
|
|
|
|
|
Difference between CPU, Reads and duration of SQL:Stmtcompleted and SP:StmtCompleted