Solved

Migration options from sharepoint 3.0 to 2010 with Large Db's

Posted on 2014-04-02
7
29 Views
Last Modified: 2016-06-04
I am looking for the best options to upgrade/migrate from 3.0 to 2010 with DB's that appear to be in the size of

Search - 1gb
Config - 33gb
Sharewebdb - 42gb

I am not sure why it is so large since it is not a big company but this seems to be huge.
I am wanting to do a db attach option to upgrade and I think i can do this if I upgrade to sql server 2008, but i am not sure if this would still be to large.
What are the best options to do this upgrade?

Thanks,
Randy
0
Comment
Question by:CREATiVENESS
  • 4
  • 2
7 Comments
 
LVL 29

Accepted Solution

by:
QPR earned 500 total points
ID: 39973763
Here are the options/steps for the upgrade itself
http://technet.microsoft.com/en-us/library/cc303309(v=office.14).aspx

Very large config DB is a known issue try this URL
http://felixyon.blogspot.co.nz/2010/06/shrinking-sharepoint-config-db-log-file.html

It also helps with Sharewebdb

My guess is that a majority of your DB size is due to timer job history and/or transaction log size. You'll certainly want to address these sizes before an upgrade
0
 

Author Comment

by:CREATiVENESS
ID: 39975517
Hi QPR,
Thanks for the info, I am aware of the different options for the upgrade but my question is what is the best option when dealing with large dbs.
I was hoping to get an opinion from someone who has actually done this also since everywhere I read tells me that it may or may not fail if I have sql server 2008 instead of express.
I am working on shrinking the dbs as it says.

Randy
0
 
LVL 29

Expert Comment

by:QPR
ID: 39975902
And the second URL I posted showed exactly how to shrink your DBs prior to upgrade
0
The Eight Noble Truths of Backup and Recovery

How can IT departments tackle the challenges of a Big Data world? This white paper provides a roadmap to success and helps companies ensure that all their data is safe and secure, no matter if it resides on-premise with physical or virtual machines or in the cloud.

 
LVL 29

Expert Comment

by:QPR
ID: 39975906
And I have shrunk thousands of transaction logs I am a DBA by trade
0
 

Author Comment

by:CREATiVENESS
ID: 39976930
Thanks qpr, I was able to get it down to about 3 gb's.
Any idea if the database attach or the in place upgrade is the better option for me now?

Thanks,
Randy
0
 
LVL 29

Expert Comment

by:QPR
ID: 39976962
Attach! The in-place upgrade creates nightmares (personal experience) in fact I think they dropped that option in 2013
0

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Introduction SQL Server Integration Services can read XML files, that’s known by every BI developer.  (If you didn’t, don’t worry, I’m aiming this article at newcomers as well.) But how far can you go?  When does the XML Source component become …
Ever needed a SQL 2008 Database replicated/mirrored/log shipped on another server but you can't take the downtime inflicted by initial snapshot or disconnect while T-logs are restored or mirror applied? You can use SQL Server Initialize from Backup…
Using examples as well as descriptions, and references to Books Online, show the documentation available for date manipulation functions and by using a select few of these functions, show how date based data can be manipulated with these functions.
This videos aims to give the viewer a basic demonstration of how a user can query current session information by using the SYS_CONTEXT function

776 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question