We have a database that was set up to use full recovery and my guess is that the reasoning was only to prevent data loss if a failure happened between backups.
We make daily full backups of the database and we have no need to recover to any point in time previous to our last backup.
Our data files and log files are in the same hard drive. From my experience (as programmer, I'm not a DBA), most database failures I've seen were related to disk failures and so I wonder if this setup makes sense. I imagine that if the hard drive fails, we wouldn't be able to recover using the transaction logs.
So my question is twofold:
- Is the most likely cause of a database failure is a hard drive failure or are there other common reasons that would justify this setup?
- Would it make more sense to switch to the simple recovery model and convince the business that in the worst case scenario they would have to re-input data for the day?