differences between RPC and SP in profiler

I am trying to capture sprocs being called in profiler. Why do I need
RPC:Completed as an example and not SP:Completed ? Wouldnt SP:completed
capture all the stored procedures ? What does RPC:completed do ? Please
provide any and all info you can about the differences..
Bring up the profiler trace that was captured during the time the System Monitor log was also captured, group it by CPU, and look at the large CPU values for the RPC:Completed or the SQL:BatchCompleted events. This will indicate the queries that are CPU i
ntensive.
When a SQL statement calls a stored procedure using the ODBC CALL escape clause, the SQL driver sends the procedure to SQL Server using the remote stored procedure call (RPC) mechanism. RPC requests bypass much of the statement parsing and parameter proce
ssing in SQL Server and are faster than using the Transact-SQL EXECUTE statement--
Satya SKJ
Visit http://www.sql-server-performance.com for tips and articles on Performance topic.
"Hassan" wrote:

> I am trying to capture sprocs being called in profiler. Why do I need
> RPC:Completed as an example and not SP:Completed ? Wouldnt SP:completed
> capture all the stored procedures ? What does RPC:completed do ? Please
> provide any and all info you can about the differences..
>
>

differences between RPC and SP in profiler

I am trying to capture sprocs being called in profiler. Why do I need
RPC:Completed as an example and not SP:Completed ? Wouldnt SP:completed
capture all the stored procedures ? What does RPC:completed do ? Please
provide any and all info you can about the differences..Bring up the profiler trace that was captured during the time the System Mon
itor log was also captured, group it by CPU, and look at the large CPU value
s for the RPC:Completed or the SQL:BatchCompleted events. This will indicate
the queries that are CPU i
ntensive.
When a SQL statement calls a stored procedure using the ODBC CALL escape cla
use, the SQL driver sends the procedure to SQL Server using the remote store
d procedure call (RPC) mechanism. RPC requests bypass much of the statement
parsing and parameter proce
ssing in SQL Server and are faster than using the Transact-SQL EXECUTE state
ment--
Satya SKJ
Visit http://www.sql-server-performance.com for tips and articles on Perform
ance topic.
"Hassan" wrote:

> I am trying to capture sprocs being called in profiler. Why do I need
> RPC:Completed as an example and not SP:Completed ? Wouldnt SP:completed
> capture all the stored procedures ? What does RPC:completed do ? Please
> provide any and all info you can about the differences..
>
>

differences between RPC and SP in profiler

I am trying to capture sprocs being called in profiler. Why do I need
RPC:Completed as an example and not SP:Completed ? Wouldnt SP:completed
capture all the stored procedures ? What does RPC:completed do ? Please
provide any and all info you can about the differences..Bring up the profiler trace that was captured during the time the System Monitor log was also captured, group it by CPU, and look at the large CPU values for the RPC:Completed or the SQL:BatchCompleted events. This will indicate the queries that are CPU intensive.
When a SQL statement calls a stored procedure using the ODBC CALL escape clause, the SQL driver sends the procedure to SQL Server using the remote stored procedure call (RPC) mechanism. RPC requests bypass much of the statement parsing and parameter processing in SQL Server and are faster than using the Transact-SQL EXECUTE statement--
--
Satya SKJ
Visit http://www.sql-server-performance.com for tips and articles on Performance topic.
"Hassan" wrote:
> I am trying to capture sprocs being called in profiler. Why do I need
> RPC:Completed as an example and not SP:Completed ? Wouldnt SP:completed
> capture all the stored procedures ? What does RPC:completed do ? Please
> provide any and all info you can about the differences..
>
>