January 23, 2009 at 5:17 am
hi m having an activity which is having a performance issue ...
i hav check the counters ..wat need to be done got confused.. wer shud i start from..
Disk Reads/sec350
Disk Writes/sec11
Split IO/Sec11
Paging File
% usage31.646
% Usage Peak28.61
Memory\\Available Bytes79646208
Memory\\Pages Input/sec0
Memory\\Pages/sec38
checkpoint pages/sec260
lazy writes/sec9
Memory Manager
Sql cache memory682
TargetServer Memory3551424
TotalServer Memory3551424
Plan Cache
Cache Hit Ratio78
SQL Statistics
Errors/sec0
SQL Statistics
Batch Requests/sec30.001
January 23, 2009 at 1:34 pm
Why do you think you have a performance issue?
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
January 23, 2009 at 1:37 pm
What activity is it? with that I mean to ask if its a query or SP or job that is taking too long all of a sudden..
Also as Gail said why do think it is a performance issue all of a sudden...
Thanks!!
The_SQL_DBA
MCTS
"Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives."
January 23, 2009 at 9:27 pm
the sp which was running was taking 1 hr rite now it is taking 7 hrs to complete...
January 24, 2009 at 1:18 am
Is there any blocking?
Has the volumes of data changed?
Are your indexes defragmented and your stats up to date?
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
January 24, 2009 at 12:41 pm
samsql (1/23/2009)
the sp which was running was taking 1 hr rite now it is taking 7 hrs to complete...
There's a thousand things that can cause that to happen. Find out what changed and you will have your answer.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 24, 2009 at 12:47 pm
samsql (1/23/2009)
the sp which was running was taking 1 hr rite now it is taking 7 hrs to complete...
Sam - Now would be a time to work through the execution plan for that stored procedure to make sure that it has all the indexes that it needs. You might be able to pick up where one might be missing / dropped.
Additionally, without having any baseline data from which to work from it is hard to say whether your server is behaving "normally" or not as we don't know what "normal" is. Know what I mean.
So, start simple. Focus on the stored procedure getting it to perform the best you can. If you want you can save the execution plan out to a file from SSMS. Rename it with a .txt extension and attach it here so that we can look at it.
Thanks.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply