Procedure profiling shows you how long it takes your procedures, user-defined functions, events, system triggers, and triggers to execute. You can also view line-by-line execution times for these objects, once they have run during profiling. Then, using the information provided in the procedure profiling results, you can determine which objects should be fine-tuned to improve performance within your database.

Procedure profiling can also help you analyze specific database procedures (including stored procedures, functions, events and triggers) found to be expensive via request logging. It can also help you discover expensive hidden procedures, for example, triggers, events, and nested stored procedure calls. As well, it can help pin-point potential problem areas within the body of a procedure.

Procedure profiling results are stored in memory by the database server and can be accessed either via Application Profiling mode in Sybase Central (the recommended method), or using functions and system procedures. Profiling information is cumulative, and accurate to 1 ms. This section explains how to perform procedure profiling via Application Profiling mode.

You can also perform procedure profiling using SQL commands. See Procedure profiling using system procedures.