Post-Update Tasks for SAS MDM

Evolve the database schema

Determine which release you are starting from, and evolve the schema for each intervening release. For instance, if you are starting from 4.1, you must run the evolve_schema batch jobs for SAS MDM 4.1, 4.1m1, and 4.2; see the table below for more information. Be sure to check the logs for the schema evolution scripts between each step to ensure that no errors occurred. If there are errors, correct them before continuing. Run these batch jobs to schema-evolve the previous SAS MDM schema. These jobs appear in the batch_jobs/sasmdm folder. Modify the echo node at the top of the job according to the instructions in the job.

If you are starting from	then you must run these jobs
SAS MDM 4.1	evolve_schema_41.djf, evolve_schema_41m1.djf, and evolve_schema_42.djf
SAS MDM 4.1m1	evolve_schema_41m1.djf, and evolve_schema_42.djf
SAS MDM 4.2	evolve_schema_42.djf

Note: Because of the addition of relationship type attributes, values in the MDM_REL_TYPE table must be sized to 23 characters or less to run the schema evolve process successfully. If you have values in the MDM_REL_TYPE table larger than 23, change the column size before attempting to run the schema evolve script. Only the underscore special character is allowed. Remove any other special characters in the MDM_REL_TYPE table before attempting to execute the schema evolve script.

Republish all entity types.

You must manually publish all of the entity types to incorporate a new clustering rule for this release in the database tables.
Regenerate all jobs.

You must manually move modifications that you have made to the standard generated output to the newly generated jobs. If the Remediation node is active in other SAS MDM jobs because of customizations, those jobs must be manually modified as well. If the Remediation node is used, you must modify these jobs through the Advanced Properties settings of the Remediation node.
Regenerate entity-specific jobs using the Data Model component.

MDM system-level jobs are updated in your Data Management Studio and Data Management Server MDM repositories. Backup directories were created for you when you ran the automated installation process. Entity-specific MDM jobs are not automatically updated. Previous customizations must be manually migrated to the newly generated jobs.
(Optional) When migrating to SAS MDM 4.3, the sample data needs to be loaded into the database. If you have already loaded the sample entity types by running the add_sample_meta.djf batch job, then you do not want to run that job again (loading the sample entity types again will result in errors).

To load only the sample data into the database, run the final two nodes of the add_sample_meta.djf batch job. To run the node, right click on the node and select Run Node.
Manually upload modified workflow templates to the workflow server using SAS Workflow Studio.

Modifications to the workflow templates used by SAS MDM support the pass-through of URL data from SAS MDM. See post-installation Step 11 for more information about how to do this. If you made customizations to your workflow templates and have them in production, review the new MDM workflow templates to see whether you must manually edit your customized workflows to perform correctly with the newer SAS MDM functionality.
(Optional) If you are upgrading to a newer QKB, you might need to increase the column lengths for standardize and match code columns in the hub. Review the documentation for both your current and the new QKB to see whether the definitions that you are using with your SAS MDM entity have changed. If the definitions have changed, perform the following steps:
1. Modify the column lengths for standardize and match code columns in your entity tables.
2. Update the columns length metadata for the affected entities in the Data Model component.

Note: After the installation is upgraded, all users of the Data Management Console must clear their browser caches.

Last updated: April 19, 2017