About SQL Tracing
[This documentation is for preview only, and is subject to change in later releases. Blank topics are included as placeholders.]
SQL tracing is a tool you can use in your load tests to help you monitor and improve the performance of your Web applications. You should use SQL tracing only if your Web application uses SQL Server to store data.
SQL tracing is not restricted to Web tests. Unit tests for applications that access SQL Server databases are also good candidates for SQL tracing.
You can collect SQL trace data during a load test run to analyze later. Collecting trace data lets you identify the slowest running queries and stored procedures in the SQL Server database being tested. You enable tracing by editing your load test in the Load Test Editor after you create it. For more information, see How to: Integrate SQL Trace Data.
If SQL tracing is enabled, a file is created during the load test run that contains the trace data. This data is automatically saved in the Load Test Results Store at the end of the test run and the trace file is then deleted. You analyze the trace data in the SQL Trace table after your load test has completed. For more information, see How to: View SQL Trace Data from a Load Test Run.