A guide to recover a database out from Suspect mode

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » Article Discussions » Article Discussions by Author » Discuss content posted by UTSAB... » A guide to recover a database out from...

43 posts, Page 5 of 5

«««1 2 3 4 5

A guide to recover a database out from Suspect mode

Rate Topic

Display Mode

Topic Options

Author

Message

Paul Randal

Posted Thursday, February 11, 2010 8:41 AM

SSCommitted

Group: General Forum Members
Last Login: Tuesday, May 14, 2013 1:23 PM
Points: 1,905, Visits: 1,601

Well of course they do - no-one was saying SQL Server is infallible - just that it doesn't fail in the way described.

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

Post #864113

DMarvez

Posted Thursday, February 11, 2010 8:52 AM

SSC Rookie

Group: General Forum Members
Last Login: Monday, May 13, 2013 10:15 AM
Points: 40, Visits: 264

Cars break (or don't brake, thank you Toyota, Honda, Ford), planes break (Boeing, Airbus), my bones have been broken (Mom).

It all comes down to using the best practices to try and keep everything humming along and minimizing the hicups that all software, hardware will eventually suffer.

Having a preventive process in place and the resources, knowledge and processes to lean on when something does break is the key to restful nights and happy
bosses and customers.

Dave

Post #864121

TravisDBA

Posted Thursday, February 11, 2010 9:09 AM

Ten Centuries

Group: General Forum Members
Last Login: Thursday, May 09, 2013 9:23 AM
Points: 1,288, Visits: 2,996

Malcolm Daughtree (2/10/2010)

The more I read on this thread the more worried I become... do you actually believe this ...?

RUNNING OUT OF DISK SPACE WILL NOT SEND YOUR DATABASES SUSPECT.

Come on guys read Books on line, buy an Admin guide, heck fill a disk drive and see what happens. Thankfully its comments like these that keep employers worried and me employeed.

That was not my point. Whatever the failure is or isn't, or as Paul basically states "it doesn't fail in the described way" that is still no reason to not check for available apace left on drives regularly. It can head off a lot of unexpected issues from occurring. That is what I was trying to put forth. It's not so much about what exactly causes or doesn't cause a failure, it's more about installing proactive measures like I stated above to prevent them, or at least notify someone beforehand, in the first place. For example, your car engine can fail for a myriad of reasons (most of them you may not even know), and many of them may have nothing to do with dirty oil, but it would still be foolhardy for anyone to not change the oil regularly.. That is just common sense. So, regardless of whether a full drive causes a suspect database or not in any version of SQL Server, doesn't really matter, even so still check the available space on those drives regularly! :)

"Technology is a weird thing. It brings you great gifts with one hand, and it stabs you in the back with the other. ... BigGrin

Post #864130

« Prev Topic | Next Topic »

43 posts, Page 5 of 5

«««1 2 3 4 5

Permissions