DB corruption cause size to increase?

[Airforce1]

Someone is telling me that I should not use a single "C" partition on my W2K Server, but instead should have a "C" & a "D" partition so I can install SQL Server on the "D" partition, then if the database becomes corrupt and "blows up in size" it will not bring the server down (OS on "C" partition).

Has anyone ever heard of a SQL db becoming corrupt in such a way that it grows in size thereby using up all available disk space?

 

[JayKusch]

Stranger this have happened, but I personally have not seen a corrupt DB spontaneously grow to fill a disk.

I have seen DBs and TLogs grow during normal use to fill a disk though. Thus, if the DB and TLog files reside on your system disk, you could bring the whole system to it knees.

Thanks

J. Kusch

 

[Airforce1]

Thanks for your feedback. Yes, I do realize that the normal growth of the DB could become a problem. I was more interested in a situation where you have, for example, a 1 GB db on a partition with 32GBs free and could it become corrupt and suddenly grow by a whooping 31 GB, thereby, filling the partition space and killing your system. I don't think so, but I wondered since it was brought up.

 

[fluteplr]

Not that I have ever heard of. I have a better reason for putting the data on a separate partion though. It makes it a lot easier and more efficient to defrag the drive.