In SQL Server 6.x it was quite easy to invalidate sysdepends because if an sp, or view depended on a table that had been dropped and recreated sysdepends continued to reference the old id of the table. SQL Server 7.0 appears to exhibit the same behaviour. Any suggestions how to easily keep sysdepends up to date.