March 2, 2009 at 10:57 am
I have very limited resources available to me for stress testing a database away from the live environment.
What I was thinking of was to have a small application that could call the stored procedure I want to profile where each parameter has a defined range of values which the application chooses are random.
I was thinking of the application having multiple threads all calling the database layer at the same time at a user defined frequency and also making sure that each connection string had a slightly different host name to simulate multiple machines calling a single DB.
I was then going to measure the various perfmon counters.
Is this in any way a valid test?
March 2, 2009 at 11:04 am
You could also have the server spend the week-end with my parents. That would be a very fair test :D.
Isn't there a tool at redgate that does stres testing? Nothing wrong with writting your own, but if you can avoid it...
March 3, 2009 at 12:58 am
I have used a number of utilities for stress testing SQL for clients... one of the quickest tools to do some simple testing is SQLIOSim: http://support.microsoft.com/kb/231619
There are also a bunch of third party utilities for this as well. If you are trying to load test a web application hooked into your SQL environment this would be a different story, but there are tons of utilities for that as well.
You may want to check out the following article though because it goes into much more detail than I can in this post: http://www.sql-server-performance.com/articles/per/stress_test_part3_p1.aspx
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply