Hi, I'm tasked with splitting MOSS 2007 site collections in a 300GB+ content db across multiple databases so we can eventually move some of the site collections to seperate web applications.
I'm initially trying to split out an 80GB site collection. Does anyone have any experiences doing this with such large site collections and content DBs? There are two (free) approaches to do this that I've come across : 1) http://technet.microsoft.com/en-us/library/cc825327(office.12).aspx *Move site collections to a new database* This approach utilises the *stsadm* *mergecontentdbs* command to do the work. 2) http://technet.microsoft.com/en-us/library/cc508854(office.12).aspx *Move site collections* This approach utilises the SharePoint Administration Toolkit, this is done in central administration via some new application pages that are deployed with the admin toolkit, running it creates a timer job that does the work in the background and send a success/failure email at the end. I've seen contradicting arguments online that say either method can potentially *corrupt* content for large site collections. Does anyone have experience using either approach splitting massive site collections out of massive databases? Would you recommend another approach? Sezai.
_______________________________________________ ozmoss mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
