January 7, 2011 at 3:20 am
Last 24 Hrs I have monitor for SQL Server performance thru windows performance Tool.
Buffer cache hit ratio - 99 % always - it looks like sql server not extra memory.
Page reads/sec - 0 always - it looks like sql server not extra memory.
But.
Page life expectancy - 160 to 250 always -it looks like sql server not suffecient memory..
I doubt why both counters are good values, and Page life expectancy low values? Please tell me its really required additional memory?
Here attached text report.
January 7, 2011 at 3:38 am
I would first run a script and check for missing indexes. (I'm sure there are SS2K scripts out there...). Most probably a missing index issue as my first wild guess.
As a side note: are you running SQL 2000? (since you posted on an 2K forum). Just want to make sure...
January 7, 2011 at 9:23 pm
Thanks LutzM for reply...
Yes, this is SQL server 2000. I will find the script for missing index in sql 2000.
Could you please share me this missing index script on sql 2000.
Thanks for your help.
ananda
January 8, 2011 at 10:20 am
ananda.murugesan (1/7/2011)
Thanks LutzM for reply...Yes, this is SQL server 2000. I will find the script for missing index in sql 2000.
Could you please share me this missing index script on sql 2000.
Thanks for your help.
ananda
Unless there's some undocumented feature in 2000 I don't know about, I don't believe there is a "missing index script" for SQL Server 2000 and I don't believe you could build one.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 8, 2011 at 12:06 pm
AFAIK there are no missing index info gathered in sql2000.
You'll need to trace for a reference load and have that analysed by database tuning advisor (included in SQL2000).
Then evaluate those results.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
January 8, 2011 at 12:55 pm
Yep, Tuning Advisor to provide some "hints" is about all that's available with SS2K.
Isn't it amazing, how little time is needed until we forget how hard it was to tune a system?
January 8, 2011 at 1:56 pm
Just to clarify in SQL2000 it is called 'Index tuning wizard' rather than database tuning advisor
---------------------------------------------------------------------
January 9, 2011 at 3:16 am
Thank you for correcting that George.
Index tuning wizard is the correct name.:blush:
It can be found in SQLserver Profiler toolbar option "tools".
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
January 9, 2011 at 8:26 pm
ALZDBA (1/9/2011)
Thank you for correcting that George.Index tuning wizard is the correct name.:blush:
It can be found in SQLserver Profiler toolbar option "tools".
Heh... call it what you want, I actually liked the interface for the old one better.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 9, 2011 at 8:36 pm
I would actually start with this.
It will most likely give you the best bang for your time invested :
January 10, 2011 at 10:54 pm
I think what is happening is that you are needing data regularly but the IO system (largely via read-aheads I bet) is getting the data into the buffer pool in time to prevent cache hit ratio from dropping. I agree that either poor queries and/or missing indexes are a culprit here.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
January 11, 2011 at 6:36 pm
Also (just and FYI), during INSERTs, it could also be too many indexes or an index with extremely low cardinality. For example, any index where the first column has a bit datatype or only a couple of unique values regardless of datatype, will almost guarantee timeouts as the index will have to do multiple extent splits to keep the data in logical order.
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply