David,
If you have an n-tier architecture, why don't you just pass in the
this.GetType().ToString() to each s.proc call, and log those through a
logging service in the data layer?
Second option is the do a stack walk in the datalayer and identify the
callers of this code and log that info there.
- Sahil Malik
http://codebetter.com/blogs/sahil.malik/
<dwilliams@newportgroup.com> wrote in message
news:1110993428.139167.213250@g14g2000cwa.googlegr oups.com...[color=blue]
> Our organization has implemented an ASP.net application with an
> n-tiered architecture, made up of a business/data layer that calls
> T-SQL Stored procedures. We are attempting to better manage the many
> stored procedures we have written over the life of the application. To
> do this, we would like to determine which sprocs are being called from
> which asp.net page. As all Sproc calls are made through the business
> layer, we really want to map class-method dependencies on stored
> procedures, as asp.net page dependencies on class-methods in our
> business layer. (In reality multiple applications rely on the business
> layer, some are not ASP.Net applications, thus the need to map the
> class-methods.) Ultimately we would like generate a database (or
> documentation) of all asp.net pages, business layer classes and
> methods, and the stored procedures they depend on whenever we wish.
> I have done some searching for a tool that maps or documents the
> dependencies in this way, but have not found anything. I have found
> lots of documenting tools, and have used architect tools such as
> Rational XDE and Visual studio architect. I have a few ideas on how to
> implement this manually but it seems troublesome and labor intensive
> and would require to modify a lot of existing code (example:
> debug.writeline every time a sproc call is made).
> Does anyone have any suggestions either on out of the box solutions or
> a good way to do this with code? Thanks,
>
> David
>[/color]
