Experiences with SQLIOStress

Hello,
Does anybody have experience with SQLIOStress? Can I trust the results?
Testing with a VMWare-Image I got everytime some errors after short time.
Does it mean, I cannot take VMWare as a server platform?
And if I'm simulating a server crash taking parameter "O#" I every time got
errors at restarting at all of the servers. Does it mean all of the servers
are not save at power outage conditions?
With best regards
HansL
SQLIOSTRESS performs file management functions such as create, shrink, grow,
read, write in the same way that SQL Server 2000 / 2005 does. It is good for
testing out your disk subsystem and I have used it a lot to burn in new
servers to look for run length queues being too long, delayed writes/reads,
etc.
Regarding VMWare, I'd be interested in your disk backend. Is it a SAN or
local SCSI attached array? What is your RAID level(s)? In my experience with
VMWare, I have had no issues in a production environment with SQL Server with
the virtual machine itself.
Andy Price,
Sr. Database Administrator,
MCDBA 2003
"HansL" wrote:

> Hello,
> Does anybody have experience with SQLIOStress? Can I trust the results?
> Testing with a VMWare-Image I got everytime some errors after short time.
> Does it mean, I cannot take VMWare as a server platform?
> And if I'm simulating a server crash taking parameter "O#" I every time got
> errors at restarting at all of the servers. Does it mean all of the servers
> are not save at power outage conditions?
> With best regards
> HansL
|||It was only a test with VMWare workstation with a local drive.
Runnning SQLIOSTress at my workstation itself, there was no problem.
But taking a VMWare image und running it at the same workstation with a
virtual drive, I saw a lot of "stale read" errors after a short time.
"Andy Price" schrieb:
[vbcol=seagreen]
> SQLIOSTRESS performs file management functions such as create, shrink, grow,
> read, write in the same way that SQL Server 2000 / 2005 does. It is good for
> testing out your disk subsystem and I have used it a lot to burn in new
> servers to look for run length queues being too long, delayed writes/reads,
> etc.
> Regarding VMWare, I'd be interested in your disk backend. Is it a SAN or
> local SCSI attached array? What is your RAID level(s)? In my experience with
> VMWare, I have had no issues in a production environment with SQL Server with
> the virtual machine itself.
> --
> Andy Price,
> Sr. Database Administrator,
> MCDBA 2003
>
> "HansL" wrote: