views:

333

answers:

3

I ran a profiler today and found that one of my stored procedures is taking a very high CPU read (1899999) and duration (3233333).

How can I fix this problem?

+2  A: 

You could start by showing us the contents of your stored procedure...Otherwise a generic answer like "Check to see what operations are being performed and optimise accordingly" will have to do.

Jobo
A: 

you'll need to look at what the sproc does and optimize it - examine the query plans for each query/operation that it does

post it here, if you can, and let some of the SQL gurus have at it

Steven A. Lowe
+1  A: 

Hi Christine,

You're unlikely to receive a satisfactory answer to this question because:

  1. The subject line of "stored procedure" is too vague.

  2. You've given too little information about the sproc to receive a meaningful answer.

Judah Himango