Hi Martijn,

I think something like MSSQL SQL Trace is VERY VERY HAND... One thing that
I do not like in MSSQL is that the SQL Statment are captured after it's
successfull executed by the server. If a statment has something boggus than
it does not appear on SQL Trace window.

A have debugged my applications and from 3rds on clients sites just with
SQL-Trace.

I don't know how MS-SQL do this, but I think that all SQL Statments
recieved by the server are boradcasted to interested (registered) clients
in a special port, the client application filters the Statments by Host,
Application, User, etc.. So you can see remote execution, debug a
connection from a remote client, etc...

I think you should know that since Database Workbench is now for MSSSQL too...

See you !

Alexandre Benson Smith
Development
THOR Software e Comercial Ltda.
Santo Andre - Sao Paulo - Brazil
www.thorsoftware.com.br


At 12:08 09/10/2003 +0200, you wrote:

>.....
>There are a couple of things here -
>
>1) client side SQL monitoring
>
>2) client side SQL monitoring for your application
>
>3) server side SQL monitoring
>.....
>Personally, I think "3" is the coolest thing - together with quota etc
>to see which queries are "heavy" on the server etc etc...
>
>I don't know if "3" is being considered for Firebird 2 - but I guess
>it is, along with many many other things.
>
>With regards,
>
>Martijn Tonies
>Database Workbench - developer tool for InterBase, Firebird & MS SQL Server.
>Upscene Productions
>http://www.upscene.com

----------


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.524 / Virus Database: 321 - Release Date: 06/10/2003


[Non-text portions of this message have been removed]