Welcome to our new Method R Corporation blog. Here, we will blog about Method R software products, events we’re attending, our experiences, how we learn, cries for help, and whatever we think might be mutually interesting (to you and to us).

I'll contribute here personally, of course. More importantly, I intend to goad my colleagues here at Method R Corporation and perhaps some other friends into contributing as well. We'll see how that goes.

So, ...hello. And welcome.


# Bernard Antonuk 2010-10-31 11:47
That's great....If this is the wrong place to post, I apologize.
We've come up with a new twist on extending the use of 10046 trace files to debug
packaged applications where one can't get to the wrapped package..
1. Create a login trigger that turns on the trace file..2. Fire the app..3.Invoke the Profiler with the generated trace file..Problem Solved.
Reply | Reply with quote | Quote | Report to administrator
# Cary Millsap 2010-11-01 04:54
Bernard, looks great to me. Triggers are a really unusual feature, if you think about it a certain way, in that they allow you to inject your code path into someone else's code path (such as your application vendor's) without their knowledge. They're just right for doing exactly what you suggest.
Reply | Reply with quote | Quote | Report to administrator