You can construct your own SQL profiler for yours apps wich use ADO, the TAdoConnection Object has two events TADOConnection.OnWillExecute and TADOConnection.OnExecuteComplete to accomplish this task.
TWillExecuteEvent = procedure (const Connection: TADOConnection; var CommandText: WideString; var CursorType: TCursorType; var LockType: TADOLockType; var CommandType: TCommandType; var ExecuteOptions: TExecuteOptions; var EventStatus: TEventStatus; const Command: _Command; const Recordset: _Recordset) of object;
TExecuteCompleteEvent = procedure (const Connection: TADOConnection; RecordsAffected: Integer; const Error: Error; var EventStatus: TEventStatus; const Command: _Command; const Recordset: _Recordset) of object;
1) Create a New Form with a TListview and a TMemo (in this example i am use a TSynEdit for format the SQL Command)
2) Create a public procedure in your form called AddLog
procedure AddLog(const Command,CommandType,Status,CursorType,LockType:String;RecordsAffected:Integer);
and implement the procedure like this
procedure TFrmLogSql.AddLog(const Command,CommandType,Status,CursorType,LockType:String;RecordsAffected:Integer); var item : TListItem; begin ListViewSQL.Items.BeginUpdate; try item:=ListViewSQL.Items.Add; item.Caption:=FormatDateTime('DD/MM/YYYY HH:NN:SS.ZZZ',Now); item.SubItems.Add(CommandType); item.SubItems.Add(Command); item.SubItems.Add(Status); item.SubItems.Add(IntToStr(RecordsAffected)); item.SubItems.Add(CursorType); item.SubItems.Add(LockType); finally ListViewSQL.Items.EndUpdate; end; ListViewSQL.Items.Item[ListViewSQL.Items.Count-1].MakeVisible(false); //Scroll to the last line end;
3) Assign the OnChange Event of the TListView
procedure TFrmLogSql.ListViewSQLChange(Sender: TObject; Item: TListItem; Change: TItemChange); begin if ListViewSQL.Selected<>nil then SynEdit1.Lines.Text:=ListViewSQL.Selected.SubItems; end;
4) Assign the events OnWillExecute and OnExecuteComplete for you AdoConnection object.
uses TypInfo; procedure TDataModule1.ADOConnection1WillExecute( Connection: TADOConnection; var CommandText: WideString; var CursorType: TCursorType; var LockType: TADOLockType; var CommandType: TCommandType; var ExecuteOptions: TExecuteOptions; var EventStatus: TEventStatus; const Command: _Command; const Recordset: _Recordset); begin FrmLogSql.AddLog( CommandText, 'Before '+GetEnumName(TypeInfo(TCommandType),Integer(CommandType)), GetEnumName(TypeInfo(TEventStatus),Integer(EventStatus)), GetEnumName(TypeInfo(TCursorType),Integer(CursorType)), GetEnumName(TypeInfo(TADOLockType),Integer(LockType)), 0); end; procedure TDataModule1.ADOConnection1ExecuteComplete( Connection: TADOConnection; RecordsAffected: Integer; const Error: ADODB.Error; var EventStatus: TEventStatus; const Command: _Command; const Recordset: _Recordset); begin FrmLogSql.AddLog( Command.CommandText, 'After '+GetEnumName(TypeInfo(TCommandType),Integer(Command.CommandType)), GetEnumName(TypeInfo(TEventStatus),Integer(EventStatus)), GetEnumName(TypeInfo(TCursorType),Integer(Recordset.CursorType)), GetEnumName(TypeInfo(TADOLockType),Integer(Recordset.LockType)), RecordsAffected); end;
5) and the final result
February 22, 2010 at 6:08 am
More interesenting article.
I am doing some tests on two small applications that I am developing.
February 22, 2010 at 7:32 am
¿Pues colocar el código del proyecto?
Can you upload the project source code?
February 22, 2010 at 10:04 am
This is a quite tricky idea! Thanks for it.
I noticed in my app, which retrievs its data from a MS SQL Server (2000) that parameters in SQL commands are shown as question marks. Is there a way to show them in a more informative way?
February 22, 2010 at 4:31 pm
Yes is possible get the info of parameters, you must check the Command.Parameters property
February 24, 2010 at 11:59 am
Thanks Rdrigo for your answer!
The SQL statement shown whith question marks instead of the paranmters is not verry helpful for me.
And I don’t know any way to get that signs replaced by the actual parameters or their values.
February 24, 2010 at 1:39 pm
Edelklaus, I showed you how to obtain the values of the params, not display them, you must process the data and show it.
April 19, 2010 at 10:11 am
Hi Rodrigo, I think there is a problem with Command.Parameters. Everytime I try to obtain the values in a Query with Parameters I get an Access Violation. I have the same problems if I use RecordSet to obtain the data.
For example in a query with Parameters:
for i:=0 to Command.Parameters.Count-1 do
Showmessage(‘Name: ‘ + Command.Parameters.Item[i].Name);
Showmessage(‘Value: ‘ + Command.Parameters.Item[i].Value);
I never get a Showmessage (even when the compiler enter in the for).
Using Delphi 2006.
March 2, 2010 at 12:09 pm
Could it be possible to view UPDATE and DELETE statements with this profiler? if not, do you know any other way to achive that. Thanks, nice tool!.
March 2, 2010 at 12:22 pm
Yes, you can see any statement.
February 25, 2011 at 8:57 pm
hey rodrigo, i have a question about your code, the first lines that presents at the beginning of the article should be added in the application?, because my app doesnt works like yours did i’m missing something?
February 26, 2011 at 10:02 am
No, these lines only shows the definition of the TWillExecuteEvent and TExecuteCompleteEvent Events. you don’t need add these lines to the project.
March 2, 2011 at 4:58 pm
one simple question, this logger only display the queries that you execute within the same app, i thought that can listen to the executed sentences for the selected database in the adoconnection source :(
March 2, 2011 at 6:28 pm
Yes the events TADOConnection.OnWillExecute and TADOConnection.OnExecuteComplete only report event to the attached ado connection.
August 9, 2011 at 11:36 pm
This doesn’t seem to work if you loop through a TADOQuery dataset and change values, like this:
Q : TAsoQuery;
Q.SQL := ‘Select … from …’;
While not Q.EoF do
Q.Fields.AsInteger := 1;
In fact, you may have made 1000 updates but the TExecuteCompleteEvent doesn’t fire once. Any idea to get around this?
January 27, 2012 at 9:04 am
We have been using a tool similar to this for ages. It’s really good to find bottlenecks in your code as you can log the Execute and ExecuteComplete together and calculate the time taken between the two…
I’d like to know if it is possible to also log an update like ‘Walt’ has asked above.
April 20, 2012 at 7:28 am
Hi, Rodrigo, thank you.
Pingback: SQL mitloggen - Delphi-PRAXiS