How MTS Spy Works

MTS Spy implements notification sinks for the various MTS Event interfaces. These interfaces encapsulate areas of MTS functionality such as transactions, threading, and activation. See the Reference topic for more information.

MTS Spy receives notifications from the MTSEvents DLL. MTSEvents receives events from the MTS Executive and maintains an event queue. Event notifications are then dispatched to listeners, and optionally logged in the MtsAudit SQL Server table.

When events are enabled through the registry key setting, you will incur a performance cost of an extra method call per event and the memory needed to allocate the event. MTSEvents does not guarantee the delivery of an event; see the IUserInfo reference topic for more information.

Every event has a timestamp. This is the time when the event was added to the queue, not the time that it was dispatched or received.

Important You cannot use a MTS Event Sink to affect the state of a running server process. You should never call into an object returned by a MTS Event Sink. They are not intended for application-specific initialization work.