| Author |
How to catch badly performing sql
|
|
| Misbah 2006-04-03, 1:23 pm |
| Hi:
I want to know how to catch poorly performing SQL in Sybase version
12.O and above.
Thank you.
| |
| hank.du@gmail.com 2006-04-03, 1:23 pm |
| MDA tables
| |
| Misbah 2006-04-04, 11:23 am |
| Than you.
| |
| Mark A. Parsons 2006-04-04, 1:23 pm |
| For pre-12.5.0.3 dataservers you have a couple options:
1 - dbcc sqltext(<spid> ); though you may find this can be somewhat limited
in usability (it often times trunctes SQL text)
2 - use a 'sniffer' (eg, RIBO) that sits between the client and the
dataserver; the sniffer should be able to capture all submitted SQL
If you're running ASE 12.5.0.3 you have the added ability to access a
couple MDA tables:
a - monProcessSQLText - *currently* running SQL text; the amount of SQL
text you can capture depends on how large you configure 'max SQL text
monitored'
b - monSysSQLText - *current* and *recent* SQL text; the amount of recent
text depends on how large you configure 'sql text pipe max messages'
With ASE 15.0 it appears that they've done some work on 'dbcc sqltext()' so
that it provides a more complete solution than in the past. (During the
time I spent with ASE 15.0 I found that 'dbcc sqltext' was mucho improved
over the way it had been implemented in the past.)
Misbah wrote:
> Hi:
>
> I want to know how to catch poorly performing SQL in Sybase version
> 12.O and above.
>
> Thank you.
>
| |
| Misbah 2006-04-05, 9:23 am |
| Thank you, Mark. very helpful.
|
|
|
|