To answer confusion with certainty the Jedi way this is not, in this forum a danger there is of losing what sanity remains :)

To add to Mark's request logging suggestions, here some SQL that may do the trick :

-- connect to the datbase with dbisql and run -- to start request logging for all connections

CALL dbo.sa_server_option( 'RequestFilterConn', -1 );

CALL dbo.sa_server_option( 'RequestFilterDB', -1 );

CALL dbo.sa_server_option( 'RequestLogFile', 'C:UsersPublicDocumentsreq.log' );

CALL dbo.sa_server_option( 'RequestLogNumFiles', 0 );

CALL dbo.sa_server_option( 'RequestLogging', 'all' );

-- run your application .. e.g..

select * from sysobjects;

-- stop request logging

CALL dbo.sa_server_option( 'RequestFilterConn', -1 );

CALL dbo.sa_server_option( 'RequestFilterDB', -1 );

CALL dbo.sa_server_option( 'RequestLogging', 'none' );

CALL dbo.sa_server_option( 'RequestFilterConn', -1 );

CALL dbo.sa_server_option( 'RequestFilterDB', -1 );

CALL dbo.sa_server_option( 'RequestLogFile', '' );

-- import request log file into global temp tables for analysis

call sa_get_request_times('C:UsersPublicDocumentsreq.log');

call sa_get_request_profile('C:UsersPublicDocumentsreq.log');

-- review request log order by the the time it took

select * From satmp_request_time order by millisecs desc;

-- see if there was any blocking

select * From satmp_request_block;

-- list host variables

select * from satmp_request_hostvar;

-- also check aggregate view on queries with their averages etc..

select * From satmp_request_profile;