The specific content of the Database Trace log file depends on the database you are accessing and the operations you are performing. However, the log uses the following basic format to display output:
COMMAND: (time)
{additional_information}
Parameter |
Description |
|---|---|
COMMAND |
The internal command that DataWindow Designer executes to perform the database operation. |
time |
The number of microseconds it takes DataWindow Designer to perform the database operation. The precision used depends on your operating system’s timing mechanism. |
additional_information |
(Optional) Additional information about the command. The information provided depends on the database operation. |
The following portion of the log file shows the commands DataWindow Designer executes to fetch two rows from a SQL Anywhere database table:
FETCH NEXT: (0.479 MS)
COLUMN=400 COLUMN=Marketing COLUMN=Evans
FETCH NEXT: (0.001 MS)
COLUMN=500 COLUMN=Shipping COLUMN=Martinez
If you opt to include DBI Names and Sum Time information in the trace log file, the log for the same two rows might look like this:
FETCH NEXT:(DBI_FETCHNEXT) (1.459 MS / 3858.556 MS)
COLUMN=400 COLUMN=Marketing COLUMN=Evans
FETCH NEXT:(DBI_FETCHNEXT) (0.001 MS / 3858.557 MS)
COLUMN=500 COLUMN=Shipping COLUMN=Martinez
For a more complete example of Database Trace output, see “Sample Database Trace output”.
