Diagram of the SP relations

All,
Is it possible to get something like a diagram of the SP relations? I'm
working with one DB and the business logic is done so that the SP can
execute another SP inside itself, the next SP can call another one, etc. So
that we can get 3-4 different sub-layers inside one SP. If I need to make
one simple change to any SP, for example to add a new parameter, I get so
huge pleasure that it's really hard to make everything right. I need to add
these parameter correctly to all SPs, plus correct the app source code. If I
could keep some automatically generated schema with all these relations on
my desk it would be much easier to break through this crazy logic. Please
help who knows how to simplify that. Don't tell me that this approach is
stupid, I know that. :( To change anything means to redo the whole DB,
that's not acceptable now, the app is in production.
Just D.Well, you could use the dependency table but that is
often inaccurate. This isn't a dead on solution but
may provide you with a good start.
It analyzes the text of the stored procedure and orders
all of them by order of "real" dependency.
http://www.eggheadcafe.com/articles/20030609.asp
Robbe Morris - 2004-2006 Microsoft MVP C#
Earn money answering .NET questions
http://www.eggheadcafe.com/forums/merit.asp
"Just D" <no@.spam.please> wrote in message
news:wTWog.8849$Nv.6431@.fed1read10...
> All,
> Is it possible to get something like a diagram of the SP relations? I'm
> working with one DB and the business logic is done so that the SP can
> execute another SP inside itself, the next SP can call another one, etc.
> So that we can get 3-4 different sub-layers inside one SP. If I need to
> make one simple change to any SP, for example to add a new parameter, I
> get so huge pleasure that it's really hard to make everything right. I
> need to add these parameter correctly to all SPs, plus correct the app
> source code. If I could keep some automatically generated schema with all
> these relations on my desk it would be much easier to break through this
> crazy logic. Please help who knows how to simplify that. Don't tell me
> that this approach is stupid, I know that. :( To change anything means to
> redo the whole DB, that's not acceptable now, the app is in production.
> Just D.
>|||Just D wrote:
> All,
> Is it possible to get something like a diagram of the SP relations? I'm
> working with one DB and the business logic is done so that the SP can
> execute another SP inside itself, the next SP can call another one, etc. S
o
> that we can get 3-4 different sub-layers inside one SP. If I need to make
> one simple change to any SP, for example to add a new parameter, I get so
> huge pleasure that it's really hard to make everything right. I need to ad
d
> these parameter correctly to all SPs, plus correct the app source code. If
I
> could keep some automatically generated schema with all these relations on
> my desk it would be much easier to break through this crazy logic. Please
> help who knows how to simplify that. Don't tell me that this approach is
> stupid, I know that. :( To change anything means to redo the whole DB,
> that's not acceptable now, the app is in production.
> Just D.
>
This is stupid, you should redo the whole DB... ;-)
Seriously though, you can search the syscomments table to figure out
which sproc reference the one you're changing. Not the perfect
solution, but it should help you find all the things you need to change
when adding a parameter...