Enterprise Database Migration

This utility requires that Statistica Enterprise has been installed to the workstation (or server with application files installed) on which the utility is to be executed. The utility has been developed and tested with Statistica Enterprise version 8.0 and later, and is not compatible with earlier versions of the product. If migration of an older version configuration database is required, please connect and upgrade the database to the latest version of Statistica Enterprise before running the utility (backing up the database beforehand).

The contents of the Statistica Enterprise configuration database are valuable and may be difficult to replace. Therefore, it is strongly recommended that you back up your configuration database before running this utility.

The first step in the process is to ensure that system DSNs have been created for both the source and destination Statistica Enterprise configuration databases. By default, with a Statistica Enterprise installation a system DSN has been created on the workstation or server called SEWSS. This is the ODBC system DSN to which the Statistica Enterprise installation is set up to store the configurations. To create a new system DSN, use the Windows Data Sources (typically accessible through the Administrative Tools).

To connect the current Statistica Enterprise installation to a different system DSN (if you want to upgrade or confirm the other database configurations), hold down the SHIFT key and start the Statistica or Statistica Enterprise Manager application. This will force the Login dialog to show, which allows the user to define a new system DSN through which to connect. Click the Options button in the login dialog to show the DSN information and define the system DSN and database username and password (if required). Click the Test Connection button to ensure that the provided DSN information can connect to the database. Provide a Statistica username and password to log on. Note that the Login dialog will not accept a Windows username and password. It must be a Statistica user (refer to training and/or install documentation or Statistica technical support for the default admin username and password).

Note: if you are using an Oracle 9i database, we recommend using the Microsoft ODBC driver for Oracle rather than the Oracle native driver. The Oracle native driver for Oracle 9i does not properly support the CLongBrinary data type. However, this problem does not exist in the Oracle native driver for Oracle 10g or later.

Click the Source DB button and select the DSN for the source configuration database providing the correct database username and password as well as Statistica Enterprise user authentication. Select the use integration authentication option so as not to have to supply a Statistica user. The Statistica user, or integrated Statistica user, will need to have the System Administrator (SADM) permission.

Click the Destination DB button and select the DSN for the destination configuration database providing corresponding authentication information.

The system view will be loaded into the corresponding pane. As you expand each of the system view folders, all configuration types that can be migrated will be loaded into the folder. Any configuration objects that do not have system view placement or are not related to an object in the system view will not be loaded.

Each object in the source configuration database pane will have a checkbox next to it. By selecting a checkbox, you can select the object and all of its related sub-objects to be migrated to the destination configuration database. Note that by clicking on the "+" sign next to an object, you can expand the view to see the associated sub-objects.

Once you have selected the checkboxes next to the object(s) that you want to migrate, click the right arrow button between the panes of the source and destination configuration databases.

A Validation Report will first be displayed that lists the following:

• The objects that will be migrated
• Any objects of the same name that exist in the destination configuration database (these will be overwritten).
• Any paths that do not exist and will be created.
• Any objects that can’t be migrated due to missing dependent parent object.

Some examples of how objects can’t be migrated due to missing dependent parent object are:

• A Data Configuration can’t be migrated without its associated Database Connection, unless the destination configuration database has a Database Connection with the same name.
• An Analysis Configuration can’t be migrated without its associated Data Configuration.
• A Report can’t be migrated without its associated Analysis Configuration.

You can save the Validation Report to a file by clicking Save Report.

To carry out the migration, click Export Enterprise Objects.

To cancel the migration, click Close.

A Copy Report will be displayed that lists the results of migration. You can save the Copy Report to a file by clicking Save Report. Otherwise, click Close to see the updated view of the destination configuration database.