Separate Site Collections and Content Databases for PWA and Project Sites RRS feed

  • Question

  • I have a customer that has 3 different environments (dev, test, production). They would like to make it easy on themselves to migrate content between them (typically from production down to test and dev). However they don't need all the project sites in test and dev. I'm thinking of creating separate site collection (/PWA) for their PWA site (root site, PDP's, etc.) and another site collection (/projectsites) for their project sites. Both would have their own dedicated content database. This would then allow them to migrate the 4 Project Server db's and the 1 PWA content db without bringing over the sites. Would this work and is it a good practice?

    Thursday, January 20, 2011 9:10 PM


  • Yep, this should work perfectly - cannot see why it won't work :) In fact, if you have a large amount of workspaces its probably a recommended way of doing it (by doing this you can try and keep individual content DB sizes small which always helps when restores come around, as you noted)
    Friday, January 21, 2011 9:09 AM