Knowledge Base

Catalog Migration Switches for Upgrading Multiple Identical Catalog Servers

Article ID: 297472

Article Last Modified on 10/18/2002

APPLIES TO

Microsoft Commerce Server 2000 Standard Edition

This article was previously published under Q297472

SUMMARY

To provide more flexibility when you run the Catalog Migration tool, two sections have been added to the SP1Setup.ini file. These capabilities are useful in an environment in which multiple Catalog databases exist on the same site and the SQL Server computers are load-balanced.

For additional information about how to obtain the latest Commerce Server 2000 service pack, click the article number below to view the article in the Microsoft Knowledge Base:

297216 How to Obtain the Latest Commerce Server 2000 Service Pack

MORE INFORMATION

Overview

If the SQL Server computer on which the Catalog databases are running is load balanced, you must modify SP1Setup.ini so that the Catalog databases can be migrated properly.

How to Work with SP1Setup.ini

See the Commerce Server 2000 SP1 Readme for sample network topology and the steps to run the SP1Setup.exe file.
Copy all of the necessary SP1 executables and SP1Setup.ini into a temporary directory, and modify the SP1Setup.ini file in this directory.
Run SP1Setup.exe.

Notes

CSUpgradeCat_SP1.exe is the Catalog Migration tool, which can be run separately multiple times.
Catalog Migration will back up the store procedures with <stored procedure name>_CS2K_Version_[n] (where [n] is the number of times the Catalog Migration has been run.
SP1Setup.exe will copy the INI file from the temporary directory to %Commerce_Server_Root%\Update\CSUninstallSP1.

Changes

[CatalogMigration] is a new section that has been added in the SP1Setup.ini file. Under this section, you can specify the following:
```
RunCatalogMigration = Yes/No
                        
```
Default = Yes You can allow Commerce 2000 SP1 Setup to run the Catalog Migration tool or not. Setting this to No requires that the CatalogServers section to be added.
The [CatalogServers] section provides a list of SQL Servers where all the Catalog databases reside. CSUpgradeCat_SP1.exe will read SP1Setup.INI and will update the SQL servers accordingly based on information found in the [CatalogServers] section. Connection String at minimum should provide authentication, the database and server information. Under this section you can specify the following:
```
SQLServerCount = 
                    
```
SQLServerCount is the number of SQL Catalog Servers that need to be updated.
```
SQLServer[n] = 
                    
```
SQLServer[n] is the actual Connection String information.

EXAMPLE: SQLServer1 = Provider=SQLOLEDB.1;UID=sa;Password=;Initial Catalog="retail_commerce ";Data Source="Ari9";"

If there is no [CatalogServers] specified, which is the default behavior, the ConnectionString is read from the MSCSAdmin database.

The Catalog Migration tool CSUpgradeCat_SP1.exe is available as a separate executable.

Uninstall

CSUpgradeCat_SP1.exe accepts the -u switch to undo the database schema changes. Hotfixes that are applied after you uninstall will be preserved.

When you uninstall, [CatalogServers] will be read again to get all the information needed to undo the catalog schema changes.

Supplier Accelerator Hotfix

The changes made in SP1Setup.ini must be compatible with the Supplier Accelerator Hotfix.ini file. Supplier Accelerator customers should be able to modify the Hotfix.ini file with the same sections described in this article.

Keywords: kbhowto KB297472

Microsoft KB Archive/297472

Contents