A tuning job enables you to view the cost details of SQL statements on a registered data source and then select the best, or most efficient, array of execution path directives in order to make query execution faster, therefore improving the entire enterprise, overall.
A tuning job consists of a set of SQL statements and any analysis results you generate against a data source using tuning. The SQL statements and analysis results that compose a tuning job can be saved in a tuning file (.tun). This enables you to open a tuning job at a later time for inspection and analysis, to add, delete, or modify the SQL statements, or generate new execution statistics.
The following topics provide a high-level overview of the tuning process:
1 Create a New Tuning Job
2 Specify a Data Source
3 Add SQL Statements
4 Run a Tuning Job
5 Analyze Tuning Results
6 Modify Tuning Results
NOTE: For additional commands that fall outside the general tuning workflow, but may still be helpful, see Additional Tuning Commands.
TIP: For information on working with data sources such as adding and browsing them, see Working with Data Sources.