June 26, 2011 at 2:00 pm
I've been thinking of using these but wondered if they had to be installed on the sql host -- which usually leads to a delay waiting for our Systems Team to do the install.
June 26, 2011 at 3:14 pm
I wouldn't recommend running either on a box that already has SQL running on it, unless you stop SQL for the duration.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 26, 2011 at 3:25 pm
Gila, what if they run during a low usage period of time, like for instance on a day noone will use access the servers? I know that both tools are designed to be use before SQL installation, but what if you will like to run them on a system to figure out what is the I/O performance (in the case of SQLIO)?
June 26, 2011 at 3:31 pm
Stop SQL first. They are IO stress test tools, they will push the IO subsystem as hard as it can go. You don't want SQL trying to get to its files during that.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 26, 2011 at 7:06 pm
I might be able to install and run on the inactive node of our cluster
on a sunday. I'm assuming it has to be
"installed" . Running from other machines would't tax the same nics etc (netapp filer)
June 27, 2011 at 9:10 am
Cluster as in shared storage windows cluster? If so, be prepared for SQl on the active node to be slow or to fail entirely due to the IO load been placed on the storage.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply