(COMPUTERWORLD) - Like waistlines, databases almost always grow much larger than their owners ever imagined. Instead of too many carbs, it's a regular diet of stodgy and unnecessary transactional information that leads to database obesity. Serious health problems can result, such as disappearing disk space, poor performance and screaming users upset about slow access rates or queries timing out.
"Our overweight database was months away from crashing due to exceeding our production disk-space capacity," says Larry Cuda, global data archiving and migration project leader at Kennametal Inc. in Latrobe, Pa. "Management determined that we could no longer just keep throwing more disks at the problem."
The article continues at http://www.computerworld.com/softwaretopics/software/story/0,10801,90819,00.html