WSS 3.0 database is 430 GB and performance is very slow

All replies

• 

  

  0

  Sign in to vote

  Hello,

  I didn't think a content database could be over 200GB. If you have multiple site collections you can easily move them into separate content databases using PowerShell.

  Create new content database:

  New-SPContentDatabase [database name] -webapplication [web application url]

  Move Site Collection:

  Move-SPSite -identity [sitecollection url] -destinationdatabase [database name, created in previous step]

  Regards.

  ---

  Brian Jones

  Edit: Just realise you said 3.0 oops.

  Try this article. http://technet.microsoft.com/en-us/library/cc825327(v=office.12).aspx

  Regards.

  • Edited by Brian R Jones Tuesday, October 22, 2013 4:28 PM

  Tuesday, October 22, 2013 4:26 PM
• 

  

  0

  Sign in to vote

  Hi Brain,

  Thanks for your reply, we have one Site collection and have many subsites. I have come up with new design see below figure. Is there any steps I should be careful of when doing the stsadm or additional steps you recommend?

  

  ---

  erkindunya

  
  
  

  • Edited by erkindunya2010 Wednesday, October 23, 2013 10:25 AM error

  Wednesday, October 23, 2013 10:24 AM
• 

  

  0

  Sign in to vote

  Hello,

  I cannot see any reason why the steps would change based on your design. However I do not have a 3.0 environment to test against so all I can say is back up your existing databases first using SQL backup just incase you need to recover.

  ---

  Brian Jones

  • Marked as answer by erkindunya2010 Friday, October 25, 2013 10:38 AM

  Wednesday, October 23, 2013 10:30 AM
• 

  

  0

  Sign in to vote

  Hi Erkin,
  

  Your design looks good to me , however i have little concern about the process you will adopt to complete it.

  Import/ Export works well for subsite, but you need to consider about the points below be open to use some custom tool to migrate the content..

  1. Content on target will be overwritten if already exists
  2. Granularity down to web only
  3. Object GUIDs are not preserved (so some things will need to be 'fixed up' e.g. anything that references a list by GUID - ListViewWebPart, using lists with InfoPath forms)
  4. Not a backup/restore tool - although it's the option which is most like backup/restore, things like alerts, audit trail, recycle bin items, 
  5. security state, workflow tasks/state are not exported
  6. Not transactional

  Also , request you to go through the link below.

  http://www.sharepointnutsandbolts.com/2007/10/stsadm-export-content-deployment.html

  http://social.technet.microsoft.com/Forums/sharepoint/en-US/e19cde39-be74-4a73-aa74-bc1166192ffe/how-to-take-back-up-of-subsite 

  Regards,

  Jayant

  *Please remember to mark your question as answered & Vote helpful,if this solves/helps your problem.*
  

  
  

  • Edited by Jayant Prabhakar Wednesday, October 23, 2013 4:29 PM grammatical mistake
  • Marked as answer by erkindunya2010 Friday, October 25, 2013 10:35 AM

  Wednesday, October 23, 2013 11:44 AM
• 

  

  0

  Sign in to vote

  Hi erkindunya,

  In addition, you need to back up all the SharePoint databases, and fully test the split process steps in your test environment firstly, the following article should help about this topic you can take a look.

  http://www.vishalseth.com/post/2009/07/16/Getting-Ready-to-split-up-a-very-large-MOSS-2007-Content-DB-into-multiple-content-DBs.aspx

  Thanks,
  Daniel Yang
  Forum Support
  If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com. 

  ---

  We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.
  Thanks for helping make community forums a great place.
  

  • Marked as answer by erkindunya2010 Friday, October 25, 2013 10:37 AM

  Thursday, October 24, 2013 8:17 AM

  Moderator