Re: tracing

In article <9l3gho$2ai7$1_at_beast.euro.net>, "Eggie" says...
>
>Tracing does not need to be done at client side only!
>It also could be important for sysops to optimize indexes and find
>bottlenecks and such...
>
>There is however a server side trace but that's only at OCI level. I just
>would call this Oracle feature missing.. it's just not 'it'. OCI tracing for
>administrators is really useless...
>SQL 2000 and SQL 7.0 even offer CPU timinngs and page/reads/writes per
>statement.

OCI level? what trace is that? we have no "oci only" trace level. We have sql_trace=true which will for any client connected to oracle (vb using odbc, java using jdbc, whatever using whatever) will trace all of the sql -- giving you cpu timings, reads/writes per statment yadda yadda yadda.

See
http://asktom.oracle.com/~tkyte/tkprof.html

for a redirect to the exact documentation on this.

>--
>Egbert Nierop
>
>>
>> To be fair - a product is a product is a product. Oracle Server is just
 that. A
>> database server product. Not a programming/development tool product.
 Oracle
>> Developer 2000 is a product specifically for Oracle developers. And this
>> includes an PL/SQL development tool, that comes with an IDE and integrated
>> debugger.
>
>
>

--
Thomas Kyte (tkyte@us.oracle.com)             http://asktom.oracle.com/ 
Expert one on one Oracle, programming techniques and solutions for Oracle.
http://www.amazon.com/exec/obidos/ASIN/1861004826/  
Opinions are mine and do not necessarily reflect those of Oracle Corp