Take the 2-minute tour ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

I am planning to my SQL server databases (plus TLogs and TempDB) to a new LUN on our iSCSI SAN. The current LUN's used by these of these files are on their own two disk RAID 1 disk group and I'm going to a larger but shared 14 disk RAID 10 disk group. I want to measure the performance of the current configuration and the new configuration as I move each database over and ensure that I am not starting to hit any disk performance issues (or see if I am actually increasing the performance).

There are a bunch of posts on the internet on SQL performance counters such as this one, but I am really interested in just the few that are related to network/disk usage and any latency or limits that associated with disk reads/writes. What are some of the important SQL or Windows performance counters that I should look at to create a current baseline/comparison for iSCSI disk access for SQL?

share|improve this question
    
It sounds like you just need to focus on the disk counters themselves, and not anything SQL specific for starters. But I'm just going on basic thoughts, so ... –  jcolebrand Mar 19 '13 at 2:48
add comment

migrated from stackoverflow.com Mar 19 '13 at 2:03

This question came from our site for professional and enthusiast programmers.

2 Answers

up vote 2 down vote accepted

I agree with Mr. Denny.

When analyzing disk performance issues I would look into this counters.

Avg. Disk sec/Read - is the average time, in seconds, of a read of data from the disk.

Avg. Disk sec/Write - is the average time, in seconds, of a write of data to the disk.

Ideally you would be looking less than 15ms latency but in reality I have seen it as high as 30ms in Tier II storage.

Another counter is Avg. Disk Queue Length and you want see that number lower if possible.

share|improve this answer
add comment

You need to be looking at seconds per read and seconds per write. Those numbers will tell you how long the storage is taking to respond.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.