Knowledge Base

INFO: Catalog Migration Switches for Upgrading Multiple Identical Catalog Servers

Article ID: 311743

Article Last Modified on 10/29/2007

APPLIES TO

Microsoft Commerce Server 2002 Standard Edition
Microsoft Commerce Server 2000 Service Pack 2

This article was previously published under Q311743

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 Microsoft 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 Sp2setup.ini so that the catalog databases can be migrated properly.

How to Work with Sp2setup.ini

See the Commerce Server 2000 Service Pack 2 (SP2) Readme for sample network topology and the steps to run the Sp2setup.exe file.
Copy all of the necessary SP2 executable files and Sp2setup.ini into a temporary folder, and modify the Sp2setup.ini file in this folder.
Run Sp2setup.exe.

Notes

Csupgradecat_sp.exe is the Catalog Migration tool, which can be run separately multiple times.
Catalog Migration backs up the store procedures with <stored procedure name>_CS2K_Version_[n] (where [n] is the number of times Catalog Migration has been run).
Sp2setup.exe copies the .ini file from the temporary folder to %Commerce_Server_Root%\Update\CSUninstallSP2.

Changes

[CatalogMigration] is a new section that has been added in the SP2Setup.ini file. Under this section, you can specify the following:
```
RunCatalogMigration = Yes/No
                    
```
Default = Yes

You can allow Commerce 2000 SP2 Setup to run the Catalog Migration tool or not. Setting this to No requires that the CatalogServers section be added.
The [CatalogServers] section provides a list of SQL Servers where all the Catalog databases reside. Csupgradecat_sp.exe reads Sp2setup.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=<username>;Password=;Initial Catalog="retail_commerce ";Data Source="ServerName";"

Note The UID account must have the correct permissions on the database.

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

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

Uninstall

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

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

Supplier Accelerator Hotfix

The changes that are made in Sp2setup.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 that are described in this article.

Microsoft KB Archive/311743

Contents