alainmarion85
New Member
- Joined
- Jul 15, 2015
- Messages
- 1
- Thread Author
-
- #1
In the work I came up against a situation when the working database at the end of day went to the Suspect Mode. And the archive was in many hours before. To transfer it in normal mode, until isn't made repaired base it was impossible. DBCC checkdb also refused to run because the database is in this mode. What to do in this case?
Solution
- Joined
- Aug 3, 2010
- Messages
- 1,289
What version of MS SQL are you using?
Backup the database if at all possible before trying any of this, I'm not responsible if you nuke your data!
You need to login to the database as the sa user and perform some maintenance.
EXEC sp_resetstatus 'database_name';
ALTER DATABASE database_name SET EMERGENCY;
DBCC checkdb('database_name');
Backup the database if at all possible before trying any of this, I'm not responsible if you nuke your data!
You need to login to the database as the sa user and perform some maintenance.
EXEC sp_resetstatus 'database_name';
ALTER DATABASE database_name SET EMERGENCY;
DBCC checkdb('database_name');
Taylor Wallis
Well-Known Member
- Joined
- Aug 21, 2014
- Messages
- 34
You sure? I mean the primary function of DBCC DBREPAIR (you didn't mention) and DBCC CHECKDB is to fix SQL database which is tagged as suspect. How does it refuse to run?