Hi. I have an editing web application with multiple site collections (only accessible internally on a dedicated port), and I've one public facing web application (on port 80). Now I want to create several host-named site collections in the public facing web application (to limit the number of web apps in the farm), and then use content deployment jobs to push the content from the site collections on the editing web app into these host-named site collections. Does anyone have any experience with this? Do you see any issues? Regards, Frode

From what you've described, I don't see any obvious issues. I trust that answers your question... Thanks C http://www.cjvandyk.com/blog

Hi Frode10, Even if your question is about Sharepoint 2007, I want to let you know that there are some limits about content deployment for Sharepoint 2010. In this article : http://technet.microsoft.com/en-us/library/cc262787.aspx#ContentDeployment it is written that there is a limit of 20 content deployment jobs. Notes : For concurrently running jobs on paths that are connected to site collections in the same source content database, there is an increased risk of deadlocks on the database. For jobs that must run concurrently, we recommend that you move the site collections into different source content databases. The software boundaries of sharepoint 2007 (http://technet.microsoft.com/en-us/library/cc262787(office.12).aspx) doesn't state a limit for content deployment but I think that you should keep in mind the limit of Sharepoint as a guideline. Hope it helps you, MarioMon Blog/My Blog (in french) LinkedIn