Siebel Performance Tuning Guide > Tuning Customer Configurations >

Analyzing Generated SQL for Performance Issues

Performance troubleshooting is an iterative process. You need to consider performance implications during design and development. Note any changes to potentially troublesome areas, such as MVGs, business component sort and search specifications, joins, extension tables, or indexes. You then test the application to determine bottlenecks, using realistic data volumes and distribution in your test environment. Focus your testing effort on the slowest, most important, and most highly configured views.

If a performance problem is detected in testing or production, then your next step is to analyze the SQL statements being generated by Siebel applications. This is one of the most useful diagnostic tools available to you for performance analysis. For more information about analyzing generated SQL for performance issues, see:

• About Specifying SQL Logging and SQL Tagging for Siebel Application Object Manager Components
• Troubleshooting Poor Performing SQL at the Database Level Using Workload Tagging
• Specifying SQL Spooling in Siebel Developer Web Client
• Troubleshooting Performance Using SQL Trace Files
• Troubleshooting Performance Using SQL Query Plans