Podemos especificarle un fichero XML de sitios a mover y moverlos a una base de datos de contenidos VACIA por lo que podríamos hacer migraciones a Sharepoint 2010 SITE BY SITE o por Bloques.
Adjuntando esta nueva base de datos actualizamos únicamente lo que deseemos a sharepoint 2010 y así podemos migrar gradualmente los sitios poco a poco o lanzarlos en paralelo en nodos diferentes para acelerar y acortar la ventana de tiempo de parada de servicio.
Es una manera muy interesante de no arrastrar basura a sharepoint 2010.
http://technet.microsoft.com/en-us/library/cc262923(v=Office.12).aspx
Syntax
stsadm -o mergecontentdbs
-url <URL name>
-sourcedatabasename <source database name>
-destinationdatabasename <destination database name>
[-operation] {1-3}
1 - Analyze (default)
2 - Full database merge
3 - Read from file
[-filename] <file generated from stsadm -o enumsites>
Parameters
| Parameter name | Value | Required? | Description | ||
| url | A valid URL, such as "http://server_name" | Yes | URL of the Web application whose databases that you want to merge. | ||
| sourcedatabasename | A valid database name, such as "WSS_Content_1 | Yes | The database name from which site collections will be moved. | ||
| destinationdatabasename | A valid database name, such as "WSS_Content_2" | Yes | The name of the database to which the site collections will be moved. | ||
| operation | Any one of the following values:
| No | 1 - Analyze: Indicates that the command window displays the current number of site collections, the database size, the maximum number of site collections, and the number of site collections that can be added before reaching the maximum number of site collections for each content database. Also, a recommendation regarding which content database should be used for the source and which content database should be used for the destination—assuming that all site collections in the database will be moved—is displayed in the command window. This recommendation is based on which content database contains less data and therefore would be faster to move. This is the default. 2 - Full database merge: Merges the entire content database from one database to another. Once the operation is complete, the source content database still exists in Microsoft SQL Server and is still attached to the Web application. It simply has no site collections in it. 3 - Read from file: Moves only a subset of site collections from the source database to the destination database. The site collections that are to be moved should be listed in a file that is specified with the filename parameter. | ||
| filename | A valid file name, such as "sites.xml" | No | Specifies a specific site collection in the source content database you want moved to the destination database This information is obtained using the databasename parameter of the Enumsites operation.
|
Note:
