August 26, 2008 at 1:09 pm
Hi all,
Is there a way to identify the dependencies between stored procedures. I am a DBA and the Dev team has provided me with some 60 odd stored procedures that need to be moved from our DEV environment to UAT. There are some stored procedures which call other stored procedures.
I was wondering if there is a way to automatically identify which stored procedures have to be executed first, so that the other stored procedures do not error out. Also because the development team is scattered and some of the developers have either moved out or they are on a vacation, I find it difficult to manually run each procedures and then look for the error to figure out which stored procedure it is dependent on.
Is there any script or gimmick or some trick that I can run on the DEV box to identify these stored procedures.
August 26, 2008 at 1:46 pm
No gimmicks, just sql dependency tracker from redgate for us. You could use some of this info to bang something up:
http://msdn.microsoft.com/en-us/library/ms345449.aspx
Theres an example to show what x uses in y, but you could probably alter that so that it doesn't list just y, but everything that depends on x.
You might also consider setting up a staging database and testing the move there first - if you aren't doing this already.
August 26, 2008 at 3:57 pm
go to the db where these sp's are, click storedproc -> right click->view dependencies..
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply