Moss, SharePoint Database Migration issues (GO)

When the project is almost finished, everyone has to consider migrating the program and data to a formal environment deployment. However, if you are developing with SharePoint, it will produce many databases, which need to be migrated and which do not need to be migrated??

Please see:

1. Configure the corresponding data description after SharePoint has completed.

Figure 1-1

Note:

A, represents the (SSP database) that is generated when the SSP is configured. Each SSP requires a database for service-specific data.    B, represents the (search database) that is generated when the SSP is configured. In addition to the SSP database, you must also provide a separate database for frequently changing search-related data. C, the representative when the configuration of the D-item installation is completed (function specific to study). D, represents the configuration database server (generated when the configuration is installed 9). E, represents the creation of the first Web application after it has been created. F, represents the creation of a second Web application after it has been created. G, represents the creation of a third Web application after it is created. H represents the start of the Office SharePoint Services Search service.

In short, the above database except F, G (green arrows) do not need to migrate, the other (Red Arrows) need to migrate.