Set up the test system to match the production environment as closely as possible. If you plan to use a test system separate from your production system, then perform the following steps: If you choose to run the SQL Performance Analyzer on the production system, then substitute the production system for the test system where applicable.Īnalyzing the SQL performance effect of system changes using SQL Performance Analyzer involves the following steps, as illustrated in Figure 2-1:įigure 2-1 SQL Performance Analyzer Workflowĭescription of 'Figure 2-1 SQL Performance Analyzer Workflow'Ĭapture the SQL workload that you intend to analyze and store it in a SQL tuning set, as described in ' Capturing the SQL Workload'. Running SQL Performance Analyzer on a test system is the recommended approach and the methodology described here. Using a test system also ensures that other workloads running on the production system will not affect the analysis performed by SQL Performance Analyzer. Instead, consider running SQL Performance Analyzer on a separate test system so that you can test the effects of the system change without affecting the production system. However, for systemwide changes-such as a database upgrade-using a production system is not recommended. If the system change does not impact many sessions or SQL statements, then running SQL Performance Analyzer on the production system may be acceptable. Any global changes made on the system to test the performance effect may also affect other users of the system. Testing a system change on a production system will impact the system's throughput because SQL Performance Analyzer must execute the SQL statements that you are testing. You can run SQL Performance Analyzer on a production system or a test system that closely resembles the production system.

Apex sql analyzer