May 19, 2009 at 1:44 pm
Best practice to start a new thread for each problem.
What happened to the database?
Please post the output from:
select state_desc from master.sys.databases
where name ='yourdbname'
If this is a time-critical issue, you should call Product Support for assistance, as any help we're able to give you over the forums is going to involve time delays.
Thanks
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
July 22, 2010 at 9:33 am
Guys,
If I don't want any 'data loss' and want to recover the database from Suspect mode, well, how to do it? Moreover, I don't have any 'backup' of the database also...
any suggestion friends?
Thanks.
July 22, 2010 at 11:03 am
Please post your question in a new thread. Thank you.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 22, 2010 at 10:29 pm
Sure Gail..
Thanks.
August 4, 2010 at 4:17 am
Please go through this link, it may help you.
http://searchsystemschannel.techtarget.com/generic/0,295582,sid99_gci1247518,00.html
April 8, 2012 at 9:16 pm
Simple way to resolve the "msdb cannot be opened. it has been marked suspect by recovery" issue,
just run the INSTMSDB.SQL script, which is under SQL server install directory under INSTALL folder.
This script can be re-run WITHOUT causing loss of data, hence we only create the database if it missing (if the database already exists we test that it has enough free space and if not we expand both the device and the database)
Regards
Senthil Palanisamy
Singapore
Viewing 6 posts - 16 through 20 (of 20 total)
You must be logged in to reply to this topic. Login to reply