Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

STSADM -addcontentdb WSSv3

  Asked By: Mohini    Date: Oct 19    Category: Sharepoint    Views: 3697

I have a question on using STSADM and the -addcontentdb
parameter.
How long does it take to add a single content database of say 500GB!
Does anyone have any metrics on this.
Also does anyone know if there is a limit of how big the content
database can be in order to be added using STSADM in WSSv3.

Share: 

 

5 Answers Found

 
Answer #1    Answered By: Kalpana Ghatge     Answered On: Oct 19

I've never heard of any limit. database  attach is one of the three main upgrade
routes, so I would imagine it's pretty robust. As for the time, it shouldn't be
too bad. SharePoint doesn't walk through the entire 500 GB when the database is
attached. The amount of time will depend more on how many Sites, webs and
libraries are in the content  database then how large it is. I know that when
you attach the database SharePoint walks through and adds all the sites from the
sites (or is it sitemap) table and adds them to the sites table in the config
database. Besides that I don't think much else is done synchronously. The rest
is done in the background, I believe.

 
Answer #2    Answered By: Bobbie Rodgers     Answered On: Oct 19

The question  should be asked why you are adding or have a 500GB DB? I would
suggest shrinking the size to under 100GB. Some of the reasons behind why we it
is best practices to do this is :


1. DR

2. SQL Server performance
Let me know if you have questions.

 
Answer #3    Answered By: Bhumi Gokhale     Answered On: Oct 19

Breaking the content  database up isn't a bad idea either. You can use the
STSADM operation mergecontentdbs to move Site Collections from one Content DB to
another.

 
Answer #4    Answered By: Davon Henson     Answered On: Oct 19

Unfortunately the database  in question  consists of one top level
site and many subsites. STSADM in WSSv2 cannot backup and restore subsites. In
WSSv3 of course it is completely different. The thought here is to possible move
this database in WSSv3 and then start breaking it up or break it up in WSSv2
with SMIGRATE and then move the databases over to WSSv3. That is how the
question came about if STSADM is able to add  a size of a content  database that
is 500GB in size in one shot in WSSv3.

 
Answer #5    Answered By: Aakash Gavade     Answered On: Oct 19

You're taking the correct path. If you use smigrate in v2 you'll just end up
being frustrated. Bringing your 500 GB content  database over to v3 should be
fine.

 
Didn't find what you were looking for? Find more on STSADM -addcontentdb WSSv3 Or get search suggestion and latest updates.




Tagged: