I have created a SharePoint Site using Site Collection feature (http://server/sites/company/). Under this, I have created many sub-sites for various teams.Now, I want to deploy the same into another environment and give access to many users.How do I:1) Deploy/promote this site within the same server (example: Deploy from http://server/sites/company-dev/ to http://server/sites/company-prod/)2) Deploy/promote this site across different servers (example: Deploy from http://dev-server/sites/company/ to http://prod-server/sites/company/)I am guessing that for both of above options, the steps should be almost same. Please share the Best Practices for above.Thanks,KamleshWebsite: http://ceekam.com/blog

Hi,1) Deploy/promote this site within the same server (example: Deploy from http://server/sites/company-dev/ to http://server/sites/company-prod/)as I understand, in the same server means in the same farm but using another URL with the same content dbYou can extend an existing Web application if you need to have separate IIS Web sites that expose the same content to usersPlese refer to this http://technet.microsoft.com/en-us/library/cc287954.aspx#Section22) Deploy/promote this site across different servers (example: Deploy from http://dev-server/sites/company/ to http://prod-server/sites/company/)You have two initial options, doing a backup and restore within SharePoint to move the data, or doing it at the SQL/STSADM level. I prefer the latter, as it isn't nearly as inclined to fail and leaves you with more flexibilityPlease check deails here http://ahmed-ammar.blogspot.com/2009/05/how-to-move-sharepoint-content-database.htmlhope this answer your questionBest Regards, Ammar MCT http://ahmed-ammar.blogspot.com Posting is provided "AS IS" with no warranties, and confers no rights.

Ahmed, thanks for the links.For my first option, I am considering that I will have two Site Collections on same server (no farms involved). My 1st Site Collection is Dev env and 2nd Site Collection is Test env.I may also have to perform Incremental deployment (e.g. after 1st deployment/promotion, I would like to move only new sub-sites where are created newly).I will go through the links and also documentation of STSADM. Thanks,KamleshWebsite: http://ceekam.com/blog

Have further query on my Option 1 (deploy site within the same server)Is it true that extending a Web application, creates a New Web Application on the same IIS server?As given in the below illustration, I want to promote/deploy the SiteCollection1 to SiteCollection2 on the same Web Application (single-server setup).http://cid-f72f4bb11ec94af8.skydrive.live.com/self.aspx/pub-scrshots/MOSS-Deployment-Query.pngThanks,KamleshWebsite: http://ceekam.com/blog

Hi,When yo extend an existing Web application you will have a separate IIS Web sites that expose the same content to users.This action exposes the same content to different sets of users by using an additional IIS Web site to host the same content.in your case I think you need 2 Web sites having 2 separate content databases, then all what you need to do is to backup and restore from Dev to Prod either by SQL or STSADMBest Regards, Ammar MCT http://ahmed-ammar.blogspot.com Posting is provided "AS IS" with no warranties, and confers no rights.