Markus (3/14/2013)
We took over a company some years ago with 100 SQL2000 dbs. CHECKDB was never run. I found two that had minor corruption that would have not allowed them to upgrade to 2005. I got one of them fixed and one I could not. It wasn't a serious issue in MSFTs eyes and it was going away so I didn't bother. I got checkdbs scheduled and low and behold within a few months one failed. I got it fixed but the point was it happened.
An ounce of prevention is worth a pound of cure as my grandmother used to say. Expect the best, prepare for the worst. Also, employ jobs/stored procedures that check those SQL Error logs daily like clockwork!!! If there is a integrity problem developing in the early stages, you are likely to see it start to surface there first. 😀
"Technology is a weird thing. It brings you great gifts with one hand, and it stabs you in the back with the other. ...:-D"