I'm having the pleasure of working with a very sharp Consultant that has been teaching me the ways of SharePoint 2007. I know I know - old technology, but I am no SP Dev, nor have I ever been. Sure I've built a couple of WebParts and the such, but I'm now able to participate in a project that consists of three very well written SP 2007 Applications - object models mapped to business classes mapped to lists and much much more...
Yesterday, I learned that one could copy content databases from say a TEST environment back to a DEV environment to migrate data and Site Collections.
Some of the keys I learned:
- If there is a managed path created in the test environment - which there is in my Test environment called "/apps", the same managed path needs to exist in the target SP environment.
- The Site Collections that exist in the TEST environment (/apps/App1, /apps/App2 ,etc) must not be created in the target DEV environment
- To figure out what content database is tied to each Site Collection DO THIS.
- I have specific notes created for this process and will attach them soon, but basically, this site goes through the process of detaching (backup works too) the source database, moving it, restoring it and then using stsadm -addcontentdb to reattach the database to a Web App. After that, the contained Site Collections within the content db are then created.
http://sharepointsherpa.com/2008/04/18/sharepoint-2007-move-content-and-configuration-databases/
Probably pretty basic for y'all with actual SP Dev experience, new to me nonetheless:
No comments:
Post a Comment