SQL Server I/O
Hello, we have a database that contains three tables. Each table has more than 25,000,000 rows in them. All three tables are in the same file group, array, and drive. Our daily Avg physical I/O is 1,000,000. Our users are complaining that the system is slow daily. Everytime a user writes to any of thos three tables our Avg Disk Queue is 6 and that is when users start calling to complain.
What is best practice in this situation?
Is there a system table i can query to look at how many times data is pulled from any of the tables?
Software/Hardware used:
SQL Server 2005
What is best practice in this situation?
Is there a system table i can query to look at how many times data is pulled from any of the tables?
Software/Hardware used:
SQL Server 2005
ASKED:
September 24, 2010 8:36 PM
UPDATED:
September 24, 2010 9:14 PM
Answer Wiki:
No there's no metric which will tell you how many times a query is run against the table. A lot more information is needed to figure out what the problem is.
How many IOs are hitting the disk per second? How long are each of those operations taking? There are perfmon counters for both of those numbers.
Are the tables correctly indexed? Are the queries scanning or seeking the indexes?
How much RAM is there in the system? How many users are using the system at a time?
What is their definition of slow? Has it always been like this, is this new?
To see all answers submitted to the Answer Wiki: View Answer History.
RSS - Discussions Help
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
