PRB: Stored Procedure Scripts Not Generated in Dependency Order
Article ID: 168257
Article Last Modified on 2/14/2005
APPLIES TO
- Microsoft SQL Server 6.5 Standard Edition
- Microsoft SQL Server 7.0 Standard Edition
- Microsoft SQL Server 2000 Standard Edition
This article was previously published under Q168257
SYMPTOMS
In Microsoft SQL Server version 6.5 and later, scripts for stored procedures are generated in alphabetical order if the object dependencies options is not selected. When you run the script to create the stored procedures, you will get the following error message:
Msg 2007: Cannot add rows to Sysdepends for the current stored procedure
because it depends on the missing object <object name>. The stored
procedure will still be created.
This error does not affect your ability to use the stored procedures. They
will be created and you will be able to run them. You can avoid this error
message by selecting the "include object dependencies" option when the
scripts are generated. However, the script will include all other objects
that the stored procedures depend on. This may cause problems if you select
the drop objects option and the stored procedures depend on tables.
WORKAROUND
To work around this problem, do either of the following:
- Generate the scripts without including the object dependencies and
ignore the error you receive when running the script to create the
stored procedures.
-or-
- Include the object dependencies and then delete the drop and create
table sections.
Additional query words: Enterprise manager SEM DMO ::Script()
Keywords: kbprb kbusage KB168257