SQL Server Home
Suspect Mode (no icon in SQL 2005)
6/13/2006 1:07:49 PM
User(s) can reproduce this bug
In SQL 2005 when a database is in suspect mode there is no obvious way to tell (via SSMS). In SQL 2000 the word "suspect" was displayed (via Enterprise Manager) next to the database, and the respective database icon was grayed out. This is a bug in SQL 2005 SSMS. From a disaster recovery standpoint, it is very important to see immediately if a database is in suspect mode.
SQL Server 2005 - Developer Edition (32)
Windows Server 2003
Operating System Language
Steps to Reproduce
Stop the SQL Service and rename a test database .mdf file in order to simulate that the database is in suspect mode. Start the SQL service and open SSMS. Notice that there is no indication in SSMS whatsoever that the database is in suspect mode.
In SSMS, the database does not appear to be in suspect mode.
In SQL 2005 (via SSMS) I would expect (as is the case in SQL 2000 Enterprise Manager) for the database icon to be grayed out and for the word "suspect" to be depicted next to the suspect database.
to post a comment.
Please enter a comment.
on 1/21/2008 at 11:35 AM
Hello - I'm not going to be able to get this in for SQL Srever 2008. This does not mean that the information is not relevant or valid; but we are not able at this time to work on this item. Note that this issue may also be fixed as a result of some framework issues we are dealing with.
Buck Woody, SQL Server Program Manager
on 2/20/2007 at 3:55 PM
I have installed Sp2 and it still doesn’t mark the databases as suspect or any other wording.
on 7/27/2006 at 12:46 PM
We asked the SQL Server storage engine team as to what was going on and they indicated that in the scenario described, the database is really in a "Recovery Pending" state. We currently don't have a way to reflect this state in the SSMS user interface. We will look at correcting this in the next release of SQL Server.
on 6/14/2006 at 6:55 AM
Thank you for you bug report regarding suspect databases. We will investigate this for our upcomming SP2 release.
to post a workaround.
Please enter a workaround.
© 2013 Microsoft