Stress testing sql
- http://vyaskn.tripod.com/analyzing_profiler_output.htm
- SQL 2000 resource kit contained a tool DatabaseHammer
- http://www.datamanipulation.net/sqlquerystress/ SQLQueryStress is a simple, lightweight performance testing tool, designed to load test individual queries
- http://www.datamanipulation.net/sqlquerystress/documentation/documentation.asp
- http://www.sql-server-performance.com/sql_server_profiler_tips.asp
- http://developer.com/db/article.php/3490086
- http://developer.com/db/article.php/10920_3490086_2
captured some SQL events using the default replay template in one SQL server and like to replay them on a different SQL server under a different database name which is the same as the source database but is a week old
1. Since my ‘replay’ server has a different server name and a different database name, how can I instruct the profiler to run the replay using a different database name?
->You have to save trace in SQL Script format and change in QA all differences(database,etc.)
2. What are the requirements for me to run the replay successfully? For example, do I have to create the same SQL login names and/or SQL user names? What do I need to do?
->Yes you need to create logins, etc.
Pasted from <http://sql-server-performance.com/Community/forums/p/14494/83996.aspx>