Application for "Replaying" a Table

I'm on a quest to find a way to "replay" a selected time range of records
from a table. The purpose is to simulate the pace and content of the records
in the table exactly as they were parsed during run-time. The ideal solution
would read records from a source table and write them to a destination table
as per a specified pace, i.e clock speed, 1/2 clock speed, 4x clock speed.

Just looking to see if there's something available currently before I jump
in and develop my own solution.

Thanks,

ChrisYou can get about 85% of what you want from SQL Profiler, although it doesn't quite get you there without some help in the form of a small app... You might even be able to do this with a SQL script, but that would be much more of a challenge.

-PatP|||SQL Profiler isn't going to help him replay the activity. He wants some kind of load simulator.|||Yeah, a tool something like LoadRunner (http://www.mercury.com/us/products/performance-center/loadrunner/) would be ideal, but you can get better than 85% of the way there using SQL Profiler to record the data into a table, then a small app to play the captured activity into another database. Not everybody has deep enough pockets to make load testing tools a snap decision... Most of us need to budget for them, sometimes for a couple of years before we get the cool toys to play with. Having a simple kludge like I've described to show what you can do with this kind of tool makes it a lot easier to sell!

-PatP

Anyone using Quest tools ?

And if so, any pros and cons ? I have heard that Spotlight can be an
overkill on OLTP applications.
Let me know..
You are asking about Third party tools and IMHO it is better to install
evaluation edition of them and find it on your own.
In my exp. Quest tools are good enough to provide required information and
analysis.
--
Satya SKJ
SQL Server MVP.
Visit http://www.sql-server-performance.com for tips and articles on
Performance topic.
"Hassan" wrote:

> And if so, any pros and cons ? I have heard that Spotlight can be an
> overkill on OLTP applications.
> Let me know..
>
>