Hi There,

We have a large CMS database (11Gb - 10,000 postings approx) and need to
make a change which is going to affect a large part of the site.

We are also running a VBScript SDO export/import routine to move the CMS
objects from the authoring environment to the production environment.

The changes are going to cause the creation of a SDO file greater than 2GB
which exceeds the maximum allowed export as detailed in the SP2
documentation... http://support.microsoft.com/kb/830247/

I read somewhere that if we wish to move the whole site then the
recommendation is to do a database backup/restore, this is fine but how do I
then stop the export script from trying to package up all those updated
objects?

I have been looking at the TimeInterval on CmsDeployExport.Export, in this
document http://msdn2.microsoft.com/en-us/library/ms949747.aspx it says

"If the TimeInterval parameter has a value of zero (0), the export will
include all objects that have changed and been approved since the last
deployment was performed and the objects upon which they depend. If the site
has never been deployed, and you specify zero (0) for the TimeInterval
parameter, the entire site will be deployed."

Currently we have the incremental setting of 0. If I am reading this
correctly then I can set the TimeInterval to 1, run the script, and then set
it back to 0 - this would have the effect fooling the export into
interpreting that everything is up to date, hence the next export would only
include those items since the last run.

Is this correct? Is this the best way to proceed?

Thanks in advance.

Adrian

[ Post a follow-up to this message ]