I need the ability to inspect a command object before it is executed and after is executed. We have our own replication strategy that will ship of data altering sql statements to several databases and then execute them. Currently the command object executed is not available. I have altered the source to call back to my own code passing the command object, I store the parameters and start a stopwatch. After the command is executed I store the parameters and the amount of time to execute.
As far as what else it could be used for... Altering query timeout per sp... Profiling statements... I can't think of any other great use right off, but it sure would make my easier I hope it makes it into the codebase. Would it help if I said "Please!" :) Thanks Mike On 3/30/06, Ron Grabowski <[EMAIL PROTECTED]> wrote: > That code doesn't exist yet. I was only using it as an example. I'm > curious to know why you would want to use that syntax for insert and > update statements instead of the normal way of doing things. I agree it > would be a useful feature...I'm just curious what other people would > use it for. >
