What should you do?

Your database named DB1 is one of 15 databases located on a SQL Server 2005 computer named SQL1. Recently, users who work with DB1 report that they experience long query execution times. You want to reproduce and analyze this problem in a test environment that holds all copies of the production databases. You need to record the workload for an entire day on SQL1 for later execution on the test server. You must ensure that all events are captured without skipping any, even if SQL1 is under stress. What should you do?

Your database named DB1 is one of 15 databases located on a SQL Server 2005 computer named SQL1. Recently, users who work with DB1 report that they experience long query execution times. You want to reproduce and analyze this problem in a test environment that holds all copies of the production databases. You need to record the workload for an entire day on SQL1 for later execution on the test server. You must ensure that all events are captured without skipping any, even if SQL1 is under stress. What should you do?

A.
Start SQL Server Profiler on SQL1 and connect locally. Use the Tuning template. Create a filter for the DatabaseID column that is equal to the database ID of DB1. Save the trace to a table on SQL1.

B.
Start SQL Server Profiler on your computer and connect to SQL1. Use the Tuning template. Save the trace to a table on the test computer. Ensure that the Server processes trace data option is selected.

C.
Start SQL Server Profiler on the test computer and connect to SQL1. Use the Replay template. Save the trace to a file on the test computer. Ensure that the Server processes trace data option is selected.

D.
Start SQL Server Profiler on your computer and connect to SQL1. Use the Replay template. Save the trace to a file on your computer. Ensure that the Server processes trace data option is not selected.



Leave a Reply 0

Your email address will not be published. Required fields are marked *