Sharepoint 2007 Content Deployment
Hi All, We use Sharepoint 2007 for our corporate website, we have 3 webservers and 1 deployment servers. I am trying to run a content deployment to one of the servers - but it would appear the destinations SQL databases has grown to over 4GB when it should be around 1.5GB - (SQL express) due to the SQL Express limitations it fails deployment as the database becomes to large. I am wondering the best way to resolve this issue - i have tried shrinking the database but i only get back approx 50MB. I am really in a no mans land right now Thanks in advance
May 9th, 2011 10:41am

TLAFFAN, There might be many reason for this. Please check if you have a full content deployment timer job set up? Do not run "Full content deployment job" every time. It should be run only when you deploy for the first time. The incremental deployment jobs will solve this purpose. Try creating a new web application and a new site collection. Create a new "FULL Content deployment job". See if it is still 1.5 GB. Running full deployments again and again will increase the database size. Hope this helps! V
Free Windows Admin Tool Kit Click here and download it now
May 9th, 2011 10:52am

Hi V284, Thanks for the quick reply, Yes usually we would run incremental deployments, which is the case on the other two webserver - but recently they stopped running and the SQL database was hitting SQL express's limit. We only run the full deployment if there is an issue which we have been trying to run now both the incremental and full deploys fail I am have already created a new web appl and they deploy OK and stay at 1.5GB, the issue we are having is one of our developers has recently left the company and the changes that he has made require it to be on a database name "WSS_Content_80" and the IIS site has to be using port 80 Do you have any other suggestions? Thanks again Tim
May 9th, 2011 11:10am

I don't there is any other way to shrink the content databases from 4.5 GB to 1.5 GB. Running multiple full deployment jobs on the same web app has caused the DB size to grow.. You could configure the newly created the web application to be your production web app. :)V
Free Windows Admin Tool Kit Click here and download it now
May 9th, 2011 11:15am

Hi V, Thanks, thats answers my question, Tim
May 9th, 2011 11:44am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics