Stored Proc Ordering Bug

Brian DonahueBrian Donahue Posts: 6,590 New member
edited October 24, 2003 10:25AM in SQL Compare Previous Versions
Hi Wayne,

Yes, I have read somewhere that sp_recompile will update sysdepends as
well as recompile the stored procedure. I'd assume that you would have to do
the recompile in a parent-child order, knowing the way sysdepends works.

Regards,

Brian Donahue
Red Gate Technical Support

"Wayne" <[email protected]> wrote in message
news:[email protected]
> I had created a few new stored procs. Some of the stored procs called
other
> stored procs. I got the following warnings when running the sync code:
>
> Cannot add rows to sysdepends for the current stored procedure because it
> depends on the missing object 'dbo.SomeStoredProc1'. The stored procedure
> will still be created.
> Cannot add rows to sysdepends for the current stored procedure because it
> depends on the missing object 'dbo.SomeStoredProc2'. The stored procedure
> will still be created.
> Cannot add rows to sysdepends for the current stored procedure because it
> depends on the missing object 'dbo.SomeStoredProc2'. The stored procedure
> will still be created.
>
> Had the stored procs been created in the correct order - there would not
> have been this warning. Also, what impact does this have? Does that mean
> the database no longer knows what procs depend on what other procs and the
> sysdepends table is not 100%? How would I update sysdepends? Recompile
> procs?
>
> Again, good job overall guys!
>
> Wayne
>
>
This discussion has been closed.