FreeTDS Development Group

[guru AT Sisis.de]

El día Thursday, April 20, 2006 a las 10:37:26AM +0200, 
michael.peppler AT bnpparibas.com escribió:

> I see.
> 
> The next step might be to enable Sybase auditing, which can be made to log
> all SQL statements to the sybsecurity database.
> 
> Michael

Thanks for the hint. We'll give it a try to log on 'User level' 'cmdtext',
even with the risk, that ASE in case of such a performance dropout
has no time for this, we'll see. I somehow, from a lot of monitoring,
think that we just hunting some (unwanted) full table scans or other
operations where our application instructs (unwanted again) ASE to copy
over tables to temp for or'ing and others.

        matthias
-- 
Matthias Apitz / Sisis Informationssysteme GmbH
ein Tochterunternehmen der OCLC PICA B.V. Leiden (NL)
D-82041 Oberhaching, Gruenwalder Weg 28g
Fon: +49 89 / 61308-351, Fax: -399, Mobile +49 170 4527211
http://www.sisis.de/~guru/