January 2, 2015 at 8:27 pm
hi team
my stored procedure was running fine
now it is taking long time what are the steps i need to follow to check what is the problem
thanks,
pradeep
January 2, 2015 at 9:29 pm
Got details??
A rough analogy to your description is like saying that "my car used to run fine, now it doesn't." The obvious response is "What changed between when it worked well and now?"
What does your stored procedure do? Can you post the T-SQL for it?
January 2, 2015 at 9:38 pm
mpradeep23 (1/2/2015)
hi teammy stored procedure was running fine
now it is taking long time what are the steps i need to follow to check what is the problem
thanks,
pradeep
Step 1. Determine what the values of the input parameters are. (I normally do this with a quick trip to the SQL profiler).
Step 2. Call the proc using the input parameters with the "Actual Execution Plan" enabled.
Step 3. Analyze the execution plan.
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply