Thought this might be an interesting graph for some folks.
This shows the elapsed time for upgrading a content database using the database attach method. This was all done on a memory-starved, physical quad-core server with 4GB of memory that has SQL, SharePoint 2010 and Project Server 2010 on it. This is NOT a final production configuration…it is merely a test to see what issues we are going to encounter during the upgrade to 2010.
So far, it doesn’t look like Bamboo or SharePoint Solutions have their 2010 products in production yet, so we didn’t have all the binaries on the test box. But, that didn’t stop us from being able to successfully get through the database attach (mount) PowerShell command:
Mount-SPContentDatabase
Now we have to wade through the "not best practice" UI customizations that were done to our 2007 web apps. Looks like it’s time for an extreme makeover!
Are you a user? 
0 Responses to “How Long Does It Take To Attach a 90 Gigabyte Content Database in SharePoint 2010?”