We infrequently encounter a failed restore attempt (SQL 2K) which leaves the Master DB and our database restore out of sync.
We receive a "bad" DB ID when trying to access the DB after the restore failure.
Is there something I can do proactively in SQL server to rectify this problem?
thx.
We receive a "bad" DB ID when trying to access the DB after the restore failure.
Is there something I can do proactively in SQL server to rectify this problem?
thx.