About Using SQL Tagging to Trace Long-Running Queries in Siebel CRM

The SQL tagging feature in Siebel CRM provides administrators with the ability to trace the origin of long-running or slow-performing SQL statements (queries) back to a specific task and user who triggered it. This topic describes the SQL tagging feature and syntax. It also provides sample code.

After SQL tagging is enabled, tagging information is added to the SELECT statements that are generated by the Siebel Application Object Manager. When a poorly performing SQL statement is suspected, the database administrator can use this tagging information at the database level to trace which component task and user initiated the SQL without the need to reboot any Siebel Server or components. Database administrators can then find the component task log file for more in-depth analysis of the performance issue. For information about enabling SQL tagging, see Enabling and Disabling SQL Tagging.

Note: Other SQL statements generated by Siebel Application Object Manager, such as INSERT, UPDATE, and DELETE, are not tagged.