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. ...:-D"