We are trying to load test an ADO.NET client server application. SilkPerformer does not record the traffic so we are thinking of capturing the SQL statements in trace files using SQL Server Profiler and then replay the trace files in Profiler and record the traffic in bdf file.
Did anyone try this approach. Is there any known issues with this kind of recording which uses the ODBC protocol. Please share your experence.
Here are the steps we used
1. Created an application profiler for SQL Server Profiler executible with ODBC protocol
2. Replay an existing trace file in SQL Server Profiler and recorded the traffic
The only issues I've had with working with ODBC is sometimes SP doesn't get the data type right so you have to make sure your datatypes are declared correctly, and when it records the ODBCFetch function it doesn't always set it up to fetch all records from the query. Other than that it seems pretty straight-forward once you get familiar with the command sequences and parameters.
Please keep us up to date on your efforts because that would be a potentially very useful practice - recording a profiler playback - never thought of that!