Home Forums SQL Server 2005 SQL Server 2005 General Discussion SQL Server Tools - Recomendations On Stress Testing and I/O Testing On New SQL Server RE: SQL Server Tools - Recomendations On Stress Testing and I/O Testing On New SQL Server

  • August 21, 2012 at 4:30 pm

    #1528405

    Scott D. Jacobson (8/20/2012)

    YSLGuru (8/20/2012)

    Grant Fritchey (8/20/2012)

    Actually, yeah, looks like 2005 might be out. That stinks. Never noticed that before.

    Any suggestions on what to do? I need to do some comparison testing aginst the new server to see how it fares against the current DB server, to see if the same workload occurring now will run better on the new system. I was going to run a non-gui trace (server side trace) and then play it back on the new server but I'm thinking here has to be a better way to do this. I'd prefer not to pays lots of moeny to do this but if nothing else I woudl think one of the SQL sofwtare Toools vendors woudl have come up with something like this, that lets you see how the same workload on one server will do on another. Make sense?

    BTW - I have and did run SQL Imulator but thats it so far.

    Thanks

    First, I think you server side trace ides is better because it's going to behave like the actual database engine.

    That being said there are tools that will just thrash the disks if that's what you need. As Grant already mentioned, SQLIO basically did just that (a bunch of reads and writes with files of a size you specified).

    Take a look at PassMark's BurnInTest suite. It has disk tests built in. The standard and pro editions are both pretty reasonably priced.

    Maybe I assumed incorrectly that this area (comparison testing of one SQL Server vs another under the same workload) is not as traversed as I thought. I assumed this kind of comparison testing was routine but maybe not.

    What my boss wants is to see in advance of our move how the new DB server will fare against the exitsing one under the same workload. This is so as to verify that our current hardware configuration is as it shoudl be. The problem with using profiler/traces is that I have to wait for a good day (when its realy busy) to do my recording (server side trace) and as fate woudl have it we are at the slow period in our month. It will be a week before things pick back up and I can get a trace of a few hours of activity that will properly represnet what its like at our peak use times.

    Make sense?

    Thanks scott.

    Kindest Regards,

    Just say No to Facebook!