Hi Al,

Thanks for the reply.

I do lots of intergration work and was thinking about the idea of being able to have a tool that could allow a user to identify common data across more than one database. The idea was that I would configure specific fields and that when a change to one field came through I could listen for the ADO call and go away and update the other field in the other database. I know I could take different approaches but this would make it less RDBMS reliant. I think there are thousands of pitfalls I havent thought about in it but until I know whether its even possible it aint worth taken any further. One massive pitfal is that I currently manage a system and if some thid party piece of software suddenly started updating my data then I would'nt be impressed at all, so maybe its a non starter.

Interesting learning experience though, thanks again for your reply.

Regards

Jon




>>Hi All,
>>
>>I am looking at whether it is possible to have some kind of service sit on a data server and listen and monitor all the ADO connections and requests made.
>>
>>I know I can check the Connection Pool for the connections being made but can I actually get any information back from this, for example the fields which an individual ADO command is going to update?
>>
>>I've done alot of googling and reading of books and I cannot find much info anywhere, however I have found a couple of products that look like they do something similar to what I want (ipmonitor), but at the minute I cant work out how they do it.
>>
>>I want to do this programtically and it really doesnt matter what language I use to achieve this.
>
>I took a quick look at the IPMonitor site. Superficially it looks like a high-level tool used to help network admins manage their networks, not really aimed at low-level protocol- or application-level monitoring.
>
>If the traffic to the server is over IP you can view all the nitty gritties with tools like Ethereal or Snort but sorting the wheat you want from all the other chaff could be a chore. Then you have to decode the wheat.
>
>You might get a response if you posted this question on a forum at http://sysinternals.com (maybe Utilities Suggestions). It might help if you included information about the specific server you're using (e.g. SQL Server), any other apps or middleware that may be involved (e.g. MTS, IIS).
>
>Finally, a more general question - why do you want information such as "the fields which an individual ADO command is going to update"? Audit tools for popular backends can record information about changes made to the DB on a per-transaction basis. Why do you need to snoop on ADO if the backend can do it for you?