Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Load Test my server?
- Thread starter Spirit
- Start date
You generally cannot just loadtest a sqlserver. You want to load test it with whatever application(s) you will be using it for. You want to test it with the things that it will normally do, but 10,100,1000 fold. Lets say your server will host one application. you will need to simulate the interation with that server. If its a custom app, write special scripts/application/pages that will interact with it just in a bigger way.
what will this server be doing? will it be hosting one application? if so which one? Will it be hosting a website database? is it custom written or shrinkwrapped? Will it be hosting custom written interal apps? Each of those possible uses require different test plans for loadtesting. But they all have the same general plan.
Do what it will normally do but alot more.
what will this server be doing? will it be hosting one application? if so which one? Will it be hosting a website database? is it custom written or shrinkwrapped? Will it be hosting custom written interal apps? Each of those possible uses require different test plans for loadtesting. But they all have the same general plan.
Do what it will normally do but alot more.
- Thread starter
- #3
Corran,
Thanks very much for your response. Now I was wanting use this server as a print server but since it literally bounced and is no longer the stand rectangle shape I really want to harmer it to see how reliable it is.
When I first got it in this state, it would boot at all eventually I got an OS on it but it would crash regularilly losing connection to the hard drives. I now have it at a point where it has been up for 2 weeks without incident so now want it to be hammered for say another week so I can decide whether to use it as a purely Test server (Win2003 is awaiting!) or risk putting it in a live environment.
So if you know of any way to put it through its paces then please let me know.
Thanks,
Iain
P.S. It really is a bit more of a Compact DL360 now! lol
Thanks very much for your response. Now I was wanting use this server as a print server but since it literally bounced and is no longer the stand rectangle shape I really want to harmer it to see how reliable it is.
When I first got it in this state, it would boot at all eventually I got an OS on it but it would crash regularilly losing connection to the hard drives. I now have it at a point where it has been up for 2 weeks without incident so now want it to be hammered for say another week so I can decide whether to use it as a purely Test server (Win2003 is awaiting!) or risk putting it in a live environment.
So if you know of any way to put it through its paces then please let me know.
Thanks,
Iain
P.S. It really is a bit more of a Compact DL360 now! lol
so you dont have a specific app you want to test, you just want test the physical server itself.
Lets see. Since you may be putting it in a live enviornment, what will you be using it for? i would start by testing it with what ever it will be or could be used for. if its a possibilty, use em all. I would also try running a large number of transactions at the same time. These could be set up using jobs, stored procedrues and cursors. They should be doing simple and complicated selects, updates, inserts and deletes. You should also try doing some admin tasks on databases. You can do some on ones currently being used, and some not as ones you will eventually perform. If you have existing datbase you can put on them as a baseline, do that then create your transactional testing processes. It will take a bit of work to come up with all the processes to test it.
But after ive said all that. If you are unsure of a machines hardware relibility (not performance ability) but its relibility, i would not put it into production if you could help it. If you do have to, then you should put things on it that you do not care as much if it has problems and could lose all data from the last backup. You should then make sure its as backed up as possible and freeqly so that data is not lost. IF you are putting Enterprise addition on it, i would use log shipping. IF not, i would use frequent backups to a different server.
I hope this helps some.
Lets see. Since you may be putting it in a live enviornment, what will you be using it for? i would start by testing it with what ever it will be or could be used for. if its a possibilty, use em all. I would also try running a large number of transactions at the same time. These could be set up using jobs, stored procedrues and cursors. They should be doing simple and complicated selects, updates, inserts and deletes. You should also try doing some admin tasks on databases. You can do some on ones currently being used, and some not as ones you will eventually perform. If you have existing datbase you can put on them as a baseline, do that then create your transactional testing processes. It will take a bit of work to come up with all the processes to test it.
But after ive said all that. If you are unsure of a machines hardware relibility (not performance ability) but its relibility, i would not put it into production if you could help it. If you do have to, then you should put things on it that you do not care as much if it has problems and could lose all data from the last backup. You should then make sure its as backed up as possible and freeqly so that data is not lost. IF you are putting Enterprise addition on it, i would use log shipping. IF not, i would use frequent backups to a different server.
I hope this helps some.
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question