April 30, 2009 at 6:57 pm
Hi,
We are using Quest Spotlight for monitoring SQL Sevrer 2005.Iam frequently getting Paging Disk Activity Alarm as below
Physical disk #0 C: containing paging file(s) 'C:\pagefile.sys' is experiencing a high rate of I/O (33.9% busy) unrelated to paging.
Could you please tell me what this alaram mean exacltly? what to do to get rid of this error?
Thanks
April 30, 2009 at 9:45 pm
This is letting you know that the C drive which is where your Windows Page file is located is running high utilization that is not associated with the Page file directly. This can impact system performance in the event that it needs to page data from memory into the page file because the drive is already being used heavily, but isn't necessarily a sign that you have a problem. To know what might be causing the issue, you have to look at what is on the C drive. If you installed SQL Server to C:\Program Files\Microsoft SQL Server\ and you didn't move your system databases and or tempdb to another drive, that could be your problem. If you have SSIS running a package, or SQL Agent performing a task that uses that drive it could be the cause.
You really have to look at the entire picture for an understanding of what might actually be involved with causing this to trigger the alarm.
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
April 30, 2009 at 9:48 pm
looks pretty pointless to me... snooze that one.
33% isnt' that busy. If it's interfering with paging (high page in/out rates) then you may have a problem.
... not enough RAM, or misconfigured MAX Server memory setting in SQL.... make sure to leave enough for the OS.
~BOT.
Craig Outcalt
April 30, 2009 at 11:32 pm
the below link might help....
http://www.sqlservercentral.com/Forums/Topic659090-146-1.aspx
May 1, 2009 at 9:55 am
Hi,
To know what might be causing the issue, you have to look at what is on the C drive. If you installed SQL Server to C:\Program Files\Microsoft SQL Server\
It is a/a/p clustered SQL Server 2005, So We installed the all the features to C drive(because it did not allow us to choose other drive). But we have datafiles, logfiles and tempdb on separate drives.
Is that true that in Cluster we need to chose C: drive for installing the features(binaries)?
In this case what best we can do?
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply