One of my tables showed 33 dependent stored procedures before I dropped the table for a maintenance and change cycle. Is executing a CREATE on the stored procedure the only way to reestablish those stored procedure dependencies?
SQL Server's automatic dependency tracking feature isn't very reliable, and SQL Server doesn't support retrieving the information unless you recreate each object that depended on the table. Microsoft is working on removing this limitation for a future release.
2 comments
Hide comments
