Proper Order of SQL Scripts

If you choose to upgrade the OLAP Metadata Catalog manually, you must run the SQL scripts in successive release order beginning with the upgrade script applicable to your current release. This is necessary because most releases make different changes to the catalog, and changes of one release are predicated on the changes of the preceding release. However, some releases of Integration Services (Release 6.2 and Releases 6.5.2, 6.5.3, 6.5.4, 7.0, and 7.1) do not require any changes to the OLAP Metadata Catalog from the immediately preceding release. No upgrade scripts exist for these releases.

Upgrading from Integration Services Release 1.x

If you are upgrading from Release 1.x to the current release, you run the following upgrade scripts in the order listed:

oc_upgrade20_*.sql
oc_upgrade61_*.sql
oc_upgrade65_*.sql
oc_upgrade651_*.sql

Upgrading from Integration Services Release 2.0

If you are upgrading from Release 2.0 to the current release, you run the following upgrade scripts in the order listed:

oc_upgrade61_*.sql
oc_upgrade65_*.sql
oc_upgrade651_*.sql

Upgrading from Integration Services Release 6.1

If you are upgrading from Release 6.1 to the current release, you run the following scripts in succession:

oc_upgrade65_*.sql
oc_upgrade651_*.sql

Upgrading from Integration Services Release 6.5

If you are upgrading from Release 6.5 to the current release, you run the following script:

oc_upgrade651_*.sql

Caution!

After you update an OLAP Metadata Catalog, you cannot roll back to a previous version. The new version of OLAP Metadata Catalog is not compatible with previous releases of Integration Services. In addition, do not attempt to use the new catalog with previous releases of Integration Services software. Such an attempt can result in corrupted OLAP Metadata Catalog data.