Jun 5, 2014 10:18:00 PM by Richard To
In SQL Optimizer for SQL Server, we have built a very sophisticated test run facility for users to find the best SQL alternative from all generated SQL alternatives to solve the user’s specific problem. But I have found that many users are just looking for SQL alternatives to improve their SQL elapsed time without fully understanding the test run function. Here are some examples to explain how various SQL test run methods solve different SQL performance problems:
There are still many other tuning purposes that require the test run method to be configured properly. In current versions of SQL Optimizer, we rely on the users experience to select the correct test run methods but some users may not have this specific knowledge of converting performance symptoms to test run methods. To help these users, we will provide a test run wizard in coming releases to help our users to configure test run methods correctly for their environment. With the following "USAGE AND SYMPTOMS" page, users will be able to input more information about the SQL performance symptoms and the SQL usage patterns, SQL Optimizer will help users to determine what test run setting is the best fit for the SQL statement. This new approach can help users quickly pinpoint the best solution for their specific environment. It also turns complicated SQL tuning scenarios into simplified questions without requiring the user to have SQL tuning knowledge.
Written by Richard To
Richard specializes in using AI technique to solve database performance problems.