[
https://issues.apache.org/jira/browse/IBATISNET-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601513#action_12601513
]
Ron Grabowski commented on IBATISNET-190:
-----------------------------------------
If you want simple performance numbers you could add an interceptor (see
Castle.DynamicProxy) to the ISqlMapper instance that listens for and times the
Query... methods.
> Add SQL execution time to debug SQL statement logging
> -----------------------------------------------------
>
> Key: IBATISNET-190
> URL: https://issues.apache.org/jira/browse/IBATISNET-190
> Project: iBatis for .NET
> Issue Type: New Feature
> Components: DataMapper
> Affects Versions: DataMapper 1.5.1
> Reporter: Mark McConnell
> Assignee: Gilles Bayon
> Priority: Minor
>
> We frequently encounter poorly performing SQL which is difficult to find.
> This can be caused by many things and execution time can change depending on
> conditions due to several factors including: indexes, clustering, table size,
> triggers etc...
> Adding SQL execution time to debug logging would help us pin point what
> statements are long running.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
