Have you checked out Microsoft's stress tool. Called WAS. Do a search here to find out more info. It is free but I am not sure of its monitoring capabilities and if it can tests databases. I do not see what it should not, but since I do not use it I am not 100% on it.
Simple minds, Simple thoughts!
I figure if you have the courage to get out of bed in the morning, then how bad can the day be.
Most LoadTest tools that support either ODBC or the Oracle native protocol would do.
You'll basically write the script from the ground up, put your timers in and run.
Writing your own little app (VB) or set of scripts(PL/SQL) could be a cheap solution. You can install this app/script on multiple workstations (or multiple instances on 1 workstation) and just let it pound the database.
You did not mention how heavy a load you are supposed to create, but an app hammering away could already create a significant load (comparable to many "normal" users).
Hope this helps.
[This message has been edited by rstens (edited 02-21-2002).]
Any tool/IDE which has threading capabilities and DB connectivity can do this.
As mentioned in one of the post above VB , VC etc can also be used effectively....
The approach i believe remains nonetheless same irrespective of the tool:-
1.Create a main script which spawns thread
2.Each thread reads data (which can be variable values that need to be passed to the statements of stored procedures) from a file or DB table itself
3.The main script may or may not have a rendezvous point.
The reason to have parametres passed to the query/stored procedure makes the query dynamic and removes the DB cache coming into picture