Prior to updating sysdatabases entry for database

19-Oct-2019 14:41

In this case the best solution is to restore the database from a recent backup.When this isn't possible, you should bring SQL Server in the so-called After this command you must stop and restart the SQL Server service.What happens at a low level is that SQL Server sets one of the bits in the table. A simpler case occurs when the file that hosts the database is renamed from the command prompt or Windows Explorer.In this case, you just have to restore the original file name and then manually restore the bit in the status field with this command: Keep in mind that the command above can be successful only after enabling writing to system tables.using a secondary log shipping db I'm in the process of testing our failover/disaster recover and have run into some problems.To start with, I've taken an image of our secondary server in our live SQL 2000 log shipping setup, then put the image onto identical hardware and started it up in physically isolated environment.

I ran the proc sp_resetstatus which is to "turn off the suspect flag" according to BOL. In a development environment I have a db with a large table.An update of many rows in the table brought the db down due to no available space.When I log into enterprise manager, I see that the databases are "Read-Only/Suspect".The read-only part is no surprise, and I imagine they show up as suspect because the latest files are not there (the image was a day old when I started testing and is now a week old).

I ran the proc sp_resetstatus which is to "turn off the suspect flag" according to BOL.

In a development environment I have a db with a large table.

An update of many rows in the table brought the db down due to no available space.

When I log into enterprise manager, I see that the databases are "Read-Only/Suspect".

The read-only part is no surprise, and I imagine they show up as suspect because the latest files are not there (the image was a day old when I started testing and is now a week old).

Once we restarted the server, a database alone is changed to suspect. If DBCC printed error messages, contact your system administrator. HTH, -- Andrs Taylor Hi, I tried with sp_resetstatus..