Upgrading from Earlier Versions

SAS Data Integration Studio users who are migrating to version 4.2 should take special note of the following changes:

SAS 9.1 metadata objects for external files, and any jobs that include these objects, will not be migrated. The external files must be re-registered in the 9.2 environment. Any jobs that include SAS 9.1 metadata objects for external files must be recreated in the 9.2 environment.

The Forecasting transformation is not supported in SAS Data Integration Studio 4.2. Jobs that include the Forecasting transformation will not be migrated.

User-defined job status Conditions and Actions are not supported in SAS Data Integration Studio 4.2. Jobs that include custom Conditions and Actions will not be migrated.

After migration, you will see the following changes to jobs and transformations.

All migrated transformations, including generated transformations before 3.2, are converted to use the new prompting framework. For most users, the main impact of this change is on the Options tab for transformations. It is now easier to select options from this tab. After migration, jobs with updated transformations should produce the same output as before.

Any versions of the Table Loader transformation and the SQL Join transformation created before version 3.4 are replaced with the latest versions of these transformations. After migration, jobs with converted transformations should produce the same output as before.

Any job whose process flow included a separate Report transformation, such as Correlations Report and Frequency Report, no longer have that transformation in the process flow. The need for separate Report transformations has been eliminated. After migration, jobs that used to require the Report transformations should produce the same output as before.

All jobs that were deployed for scheduling or were deployed as stored processes should be redeployed in the SAS 9.2 environment. From the SAS Data Integration Studio desktop, you can select ToolsRedeploy Jobs for Scheduling or ToolsRedeploy Jobs to Stored Processes.

Any job that was deployed as a Web Service in SAS Data Integration Studio 3.4 now appears in the Stored Process folder of the Inventory tree, not the Web service (generated) folder. This special type of stored process can be used as before.

If jobs that include the Create Match Code transformation do not run successfully after migration, verify that the appropriate Quality Knowledge Base (QKB) location value (DQSETUPLOC value), is specified on the global options window for SAS Data Integration Studio. To verify the DQSETUPLOC value, select ToolsOptions from the menu bar, click the Data Quality tab, and then verify that the appropriate value is specified in the DQ Setup Location field.

Jobs that include the Apply Lookup Standardization transformation will not run successfully after migration until you take one of the following actions:

The following additional steps are required in order for the export SAS Package method to work:

To verify these values before importing the SAS Package, select ToolsOptions from the menu bar, click the Data Quality tab, and then verify that the appropriate value is specified in the DQ Setup Location field. Then specify the appropriate values in the DQ Setup Location field and the Scheme Repository Type field. The DQ Setup Location field should specify appropriate Quality Knowledge Base (QKB) location value (DQSETUPLOC value). The Scheme Repository Type field should match the type (BFD or NOBFD) for the package of jobs that you are importing.

When the package is imported, the job and its transformations are updated as they are during migration. The Apply Lookup Standardization transformation uses the default scheme repository values, and if the values are correct the transformation runs successfully.

You might have jobs stored in locations that are not part of the migration process. If these jobs can be exported to SAS 9.1.3 Package format, you can use the Import from SAS Package wizard in SAS Data Integration Studio 4.2 to convert and register these jobs on your metadata server.

If you have jobs that were exported in XML format before SAS Data Integration Studio 3.4., you must either include these jobs in a system migration, or import them in SAS Data Integration Studio 3.4, export them as a SAS Package, then import the SAS Package in SAS Data Integration Studio 4.2.

After migration, you will see the following changes to the tree view on the left side of the desktop.

The Custom tree is now called the Folders tree. Any user-defined folders in the Custom tree now appear in the Folders tree. If a migrated or imported object was not located in a folder, and it is an object type that requires a folder, it is placed in the Shared Data folder.

My Folder is the private folder of the user who is currently logged on. Metadata in this folder is visible only to the current user and to unrestricted users. When you add a new metadata object, and you want to share it with other users, do not save it to My Folder.

In the Folders tree, you cannot have duplicate objects with the same name in the same folder. Accordingly, after migration or when importing metadata from versions before version 4.2, if there were duplicate objects with the same name in the same folder, a number will be added as a suffix to the duplicate filename (filename(1), filename(2), and so on). Also, metadata objects can no longer have slash characters in their names. If a migrated or imported object had slash characters in its name, the slashes are replaced by underscores.

Unlike the Custom tree, in the Folders tree, you cannot drag and drop objects from one top-level folder to another. Instead, you can right-click the object and select Move to Folder.

The Inventory tree now contains folders for more type of objects. Most of the time, however, SAS Data Integration Studio users work with the same objects as before, such as tables, libraries, and jobs. Some actions, such as importing metadata, can no longer be done in the Inventory tree. You must perform these actions from the Folders tree.

The Process Library tree is now called the Transformations tree. The Transformations tree supports one level of folders only. If transformations in your Process Library were organized in a hierarchy of folders, they now appear at the top level of the Transformations tree.

The Project tree, a special tree that was used under change management, is now called the Checkouts tree.

In previous versions of SAS Data Integration Studio, metadata repositories were the top level objects in the Inventory tree and the Custom tree. Now, metadata repositories are not visible in the Inventory tree, and they are just another folder in the Folders tree. In most cases it is no longer important which metadata repository contains a particular object. If you have the appropriate privilege, you can work with any object in the tree views, regardless of what metadata repository contains the object.

From this release forward, new jobs with code that is generated by SAS Data Integration Studio must be executed on a SAS 9.2 Workspace Server or newer.

Administrators who are responsible for setting up change management in SAS Data Integration Studio must do some additional work after migration. For more information, see the SAS Data Integration Studio chapter in the SAS Intelligence Platform Desktop Application Administration Guide.

Some SAS 9.2 solutions might not be available until after the release of SAS Data Integration Studio 4.2. Accordingly, if your site is using a SAS solution, it is recommended that you not import individual solution objects until that solution is ready for SAS 9.2 and is installed.

Alternatively, you can migrate or import jobs with missing solution transformations and simply not open them until after the SAS 9.2 solution is installed. After the SAS 9.2 solution is installed, you can select a job in a tree view and use the Upgrade pop-up menu option to upgrade the job.

For more information about migration, see our Migration Web site: http://support.sas.com/rnd/migration/utility/utilitynotes.