My client has been on MOSS 2007 for nearly 3 years. We're about to do an upgrade to 2010 on their system and found their content database to be around 350Gb in total. This to me seems a bit ridiculous?
If I where to try and clean up the database, not shrink, what should I generally look for that might cause this massive file size? The log file attached to the database is sitting roughly at around 20Mb which I can live with, but 350Gb for content seems a bit much, yes?