November 24, 2011 at 1:52 am
Dear All,
I have an issue regarding the procedure tuning. I tuned one procedure which retrieves 6lakh records. Previously it was taken around 8 min to give the results. After tuning that SP it was taken around 2 min 30 sec... means they said it's ok... After 1 week they restored that DB. Again i executed the same procedure, but it giving results some times it is 12 min, 8.30 sec, 5.30, 4.45sec like that...
Previously it was fine. I checked with the code the same code, nothing was changed...
Can anybody please let me know where the issue is , whether it is from Database side (Network traffic or Procedure side.....)
Advance Thanks to All,
Skase
November 24, 2011 at 2:06 am
Your question is like asking My car makes noise, what's wrong with it? & without taking it to the garage.
Did you capture both the good version and bad version of the plan (actual, not estimated)?
Was it slow right after a server recycle?
November 24, 2011 at 5:25 pm
Thank u Very Much Boss, I just taken my car to the Garage....This is not the way to give the answers for the post...
just tell the answer what u have....
November 24, 2011 at 11:41 pm
I need the good and bad execution plans (actual, not estimated).
November 25, 2011 at 12:14 am
SqlSpider... (11/24/2011)
This is not the way to give the answers for the post...
And that's not the way to reply to someone who's helping you in his spare time
just tell the answer what u have....
The point is that there is not enough information in your post to even begin to get a vague idea of what the problem could possibly be. Literally you've told us that there is a problem, given no useful information and then demanded answers. Not going to work.
Without at least the execution plans of the good and bad executions, some info on table structure and index definitions there is no way that anyone is going to be able to help you.
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 28, 2011 at 11:59 am
Not enough information to suggest a good solution. Execution plans would sure help.
"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
November 29, 2011 at 6:50 am
Since you gave us absolutely NO information that is useful for us to help you I will take a quick Wild *** Guess and say update statistics on all objects and try again.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
January 10, 2012 at 12:09 am
Try the same problem with clearing catch and buffer.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply