|
|
Posted by marcsirois on 10/12/06 12:52
Thanks Adrian,
Thanks for the reply. This is indeed helpful.
abc wrote:
> Not sure about 2005 but in 2000 use syscomments
>
> SELECT *
> FROM syscomments
> WHERE TEXT LIKE '%<your function name>%'
>
> Now add sysobjects to get the name of the stored procedure where your
> function is called. If you are using QA instead of that awful thing in
> 2005, create a stored procedure in the master database add a shortcut
> key sequence in QA, highlight the function name, press the shortcut and
> all instances will magically appear.
>
> Adrian
>
>
>
> marcsirois@gmail.com wrote:
> > I am maintaining an application where most of the business rules are in
> > Triggers, Stored Procedures and User Defined Functions. When a bug
> > arises, it can get very tedious to debug. Today for example, I wanted
> > to modify a function that was being called by a trigger. The problem
> > is that I don't want to change the function, for fear that it is being
> > called by one of the other SP's or triggers in the database (there are
> > hundreds of them)
> >
> > Essentially, I need a tool that allows me to view where functions and
> > sp's are being referenced from. At the very least, I'd like to perform
> > a "full text search" in the database objects, so that let's say I have
> > a function named "fn_doSomething", I can search the schema for this
> > string and get all the places where it appears.
> >
> > As you can see, I'm in the dark here. I've never worked on a system
> > where all business rules are at the database level. If you know of a
> > tool that does what I describe above, or anything else that would
> > facilitate my life, please let me know!
> >
> > Thanks for your help,
> >
> > Marc
> >
Navigation:
[Reply to this message]
|