*Success!* After a failed attempted (ran out of disk space on SQL Server, you need at least 3x the size of the site collection you are moving) I've got the 80GB+ DB split out of the 300GB+ DB completed and working fine.
No corruption whatsoever and I used the mergecontendb approach. 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. As long as you have no users using the farm, sufficient spec'd hardware etc. this method will work. Sezai. On Wed, Jun 23, 2010 at 8:59 AM, Paul Noone < [email protected]> wrote: > Have you considered just dumping out the libraries into new SCs using > dedicated DBs? I know it seems like overkill to create a new collection > purely for the purpose of holding a document library or two but it does have > its advantages. > > > > Regards, > > Paul > > Online Developer, ICT > CEO Sydney > > > > *From:* [email protected] [mailto:[email protected]] *On > Behalf Of *Adam Clark > *Sent:* Tuesday, 22 June 2010 3:44 PM > *To:* ozMOSS > *Subject:* RE: Splitting LARGE Site Collections into Seperate Content > Databases using Free Tools > > > > I once split a 120Gb site collection into a 40GB and 80Gb collection using > the first method. While there was no corruption in the final split, the > first two of our 5 test runs ended up in corrupt DB’s due to poor network > infrastructure. Once we ensured that the SharePoint and SQL server were on > the organisations quality core switch we had no issues. I am also assuming > that your keeping the databases on the same DB server? > > > > Also note that the database has a lot of content in it, but all of it was > under 50mb in size (lots of versions made the bulk of the size). If your > migrating larger files I don’t know how this approach would work. > > > > I have never used the second method so I can’t really comment, but reading > the article it looks pretty simple (famous last words) > > > > Regards, > > > > Adam Clark > > *Principal Solutions Architect* > > * * > > [image: Description: cid:[email protected]] > > Office: 1300 611 359 > > Mobile: +61 412 344 037 > > Email: [email protected] > > Web: http://www.sharingminds.com.au > > Blog: http://adamclark.sharingminds.com.au > > [image: Description: > Badge-Speaking-Large]<http://www.sharepointconference.com.au/> > > Proudly speaking and sponsoring the following events: > Australian SharePoint Conference <http://www.sharepointconference.com.au/>– 16 > th & 17th June > > Business Productivity Specialists with: > > [image: Description: SP2010] > > > > > > > > > > > > > > *From:* [email protected] [mailto:[email protected]] *On > Behalf Of *Sezai Komur > *Sent:* Tuesday, 22 June 2010 1:51 PM > *To:* ozmoss > *Subject:* Splitting LARGE Site Collections into Seperate Content > Databases using Free Tools > > > > 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 > >
<<image002.jpg>>
<<image001.gif>>
<<image003.png>>
_______________________________________________ ozmoss mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
