14.01.2013 Views

SAS 9.3 Guide to Software Updates

SAS 9.3 Guide to Software Updates

SAS 9.3 Guide to Software Updates

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Changes <strong>to</strong> Note Before You Upgrade <strong>to</strong> <strong>SAS</strong> Data Integration Studio 4.3 137<br />

n Any pre-3.4 versions of the Table Loader transformation and the SQL Join<br />

transformation are replaced with the latest versions of these transformations. After<br />

migration, jobs with converted transformations should provide the same output as<br />

before.<br />

n Any job whose process flow included a separate Report transformation, such as<br />

Correlations Report and Frequency Report, no longer has that transformation in the<br />

process flow. The need for separate Report transformations has been eliminated.<br />

After migration, jobs that used <strong>to</strong> require the Report transformations should produce<br />

the same output as before.<br />

n All jobs that were deployed for scheduling or were deployed as s<strong>to</strong>red processes<br />

should be redeployed in the <strong>SAS</strong> <strong>9.3</strong> environment. From the <strong>SAS</strong> Data Integration<br />

Studio desk<strong>to</strong>p, select Tools � Redeploy Jobs for Scheduling or Tools �<br />

Redeploy Jobs <strong>to</strong> S<strong>to</strong>red Processes.<br />

n Any job that was deployed as a Web service in <strong>SAS</strong> Data Integration Studio 3.4<br />

appears in the S<strong>to</strong>red Process folder of the Inven<strong>to</strong>ry tree, not the Web service<br />

(generated) folder. This special type of s<strong>to</strong>red process can be used as before.<br />

n The DataFlux IS Job transformation is now called the DataFlux Batch Job<br />

Transformation. The DataFlux IS Service transformation is now called the DataFlux<br />

Data Service transformation. For other changes related <strong>to</strong> these transformations,<br />

see Chapter 27, “Working with Data Quality Transformations,” in <strong>SAS</strong> Data<br />

Integration Studio: User's <strong>Guide</strong>.<br />

Migrate Content S<strong>to</strong>red outside the <strong>SAS</strong><br />

Configuration Direc<strong>to</strong>ry<br />

Some metadata objects specify paths <strong>to</strong> physical files. If these files are s<strong>to</strong>red outside of<br />

the direc<strong>to</strong>ries that are part of the standard migration process, then you must manually<br />

migrate the files. If a file on the target computer has a different physical path than the<br />

file had on the source computer, then any migrated metadata that points <strong>to</strong> that file has<br />

<strong>to</strong> be updated <strong>to</strong> point <strong>to</strong> the new location.<br />

For example, the metadata for a transformation within a job can point <strong>to</strong> a file that<br />

contains source code. If the file is s<strong>to</strong>red outside of the <strong>SAS</strong> configuration direc<strong>to</strong>ry, the

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!