RE: simple question about tracing queries with database manager

> -----Message d'origine-----
> De : Zabach, Elke [mailto:elke.zabach@xxxxxxx]
> Envoye : mercredi 29 decembre 2004 13:39
> A : Fabrice Bourdel; maxdb@xxxxxxxxxxxxxxx
> Objet : AW: simple question about tracing queries with database manager
> 
> 
> Fabrice Bourdel 
> > 
> > hi,
> > 
> > i have a simple question : what do i have to do to
> > simply see all queries executing on the database
> > with the database manager program ?
> > 
> > I know i has something to do with the "Database Trace"
> > I tried to check :
> >  - "DEFAULT" in "Option"
> >  - "Trace sessions = All sessions" in "Advanced"
> >  - [a] (order interface AK) in "Protocol"
> > 
> > ... and execute queries...
> > 
> > there is so less help about that that i don't really know
> > precisely what are thoses options really about...
> > 
> > i know that i should then see the results in "Diagnostic files",
> > with "Kernel trace protocol" after clicking on le flush button,
> > 
> > could you tell me what to do ?
> 
> 1. Oops, why do you want to see the queries sent by DBM? What do you
> want to know? Can we help with some info?
> 2. Database Trace will switch on some info written in the server.
> Usually the output of this is useful for developers/MaxDB-support, but
> not for customers. Therefore my first question to shorten this.
> 3. Option DEFAULT will write much more than the command itself. And as
> the trace-storing-area is written as a cycle this 'much more' can easily
> overwrite the info YOU want. For your needs not the option Default, but
> ORDER is convenient.
> 4. trace sessions = All sessions, ok
> 5. NOW do the queries
> 6. Then flush the vtrace (look for the flash-button)
> 7. NOW [a] for order interface and 'make protocol' has to be done
> 8. read Kernel Trace Protocol (if you like, but as I said before: why???
> In this case?)
> 
> Elke
> SAP Labs Berlin
> > 
> > thanks for help.
> > 
> > 
> > --
> > MaxDB Discussion Mailing List
> > For list archives: http://lists.mysql.com/maxdb
> > To unsubscribe:
> http://lists.mysql.com/maxdb?unsub=elke.zabach@xxxxxxx
> 


Thank you for your response.

I would like to see all the queries send to the database for
my application debugging/optimisation purpose.

I a perfect world, you would like to see information about
the execution time, the query plan used, this, in a "real
time" console, i would be great... a bit like the profiler
tool (with sql server from ms)
Is this kind of feature already planned by your developement 
people ?
Naturaly, i can test, execute and do timing things before
implementing, but i do not do it for all queries an such a
tool would be nice to check globally and see where there
could be hot spot...


-- 
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/maxdb?unsub=gcdm-maxdb@xxxxxxxxxxx