Thanks Glen, that gives the performance by line number, but I think I then have to manually match up line numbers to the code. Unless I'm missing something there isn't anything that either gives me them together, or lets me retrieve from a system table what SQLA reckons is on each line of the procedure. Any pointers would be a help - it becomes an issue when trying to discuss a profiling result with somebody.