Sas 9.2 eg migration v1
- 1. Migrating Enterprise Guide Projects From EG 4.1(SAS 9.1.3) to EG 4.2 or 4.3 (SAS 9.2)
- 2. Migration Options Three migration options exist: 1. Open Project in EG 4.2 or 4.3 and Save This approach is suitable if there are no required changes to Server names, Libnames, paths etc 2. Utilise the Enterprise Guide Migration Wizard This approach automatically migrates multiple EG Projects in one process 3. Manual Migration Open the Enterprise Guide 4.1 project in Enterprise Guide 4.2 or 4.3 and manually make the necessary changes
- 3. Option 1: Open in EG 4.2 and Save § EG 4.1 projects can be opened directly in EG 4.2 or 4.3 and run on the SAS 9.2 server § It is stored in EG 4.2 or 4.3 format when you save § Assumes no changes to: • Server names • Libnames • Table Names • File Paths
- 5. Option 2: EG Migration Wizard § Migrates multiple EG Projects in one process § Converts the Project file to the 4.2 or 4.3 format § Makes global changes to object references (i.e Lbraries, tables etc) § Run MigrationWizard.exe § normally in » C:Program FilesSASEnterpriseGuide4.2 • C:Program FilesSASEnterpriseGuide4.3 • no shortcut is installed when you install EG 4.2 or 4.3
- 16. EG Migration Wizard § You can record Mappings to make the process repeatable • doesn’t work in M2 • fixed in M3 § Automatically creates an Archive (backup) of the original files, still in EG 4.1 format § Can struggle with large volumes
- 17. Option 3: Manual Migration § Open in 4.2 and Save § Manual Replace server § Manually Replace Libraries § Don’t forget hardcoded libnames in code nodes § Manually repoint/relink tables § Manually repoint/relink external files § Don’t forget hardcoded file paths in code nodes § Rerun import wizard for external files
- 22. Compatibility § EG 4.1 projects can’t be run on SAS 9.2 servers § EG 4.2 projects can’t be run on SAS 9.1.3 servers § Once converted EG 4.2 projects can’t be opened in EG 4.1 § EG 4.2 no longer has the option for standalone repositories § You can run EG 4.1 and EG 4.2 on the same PC (you might experience conflicting DLLs see SAS Note 33988)
- 23. Possible Migration Issues (tricks for young players) § Import Wizard/Process completely re-written § Computed columns in Query Nodes completely re-written § Prompt framework completely re-written § Some issues with Date Formats § Watch for: § Hard coded file paths § Watch for hardcoded libname statements § Watch for linked SAS code paths § Security can be applied at a EG Function level via Metadata roles and effect migrated EG Projects
- 24. Summary § Keep server names, libnames, etc the same if you can § Use migration wizard if possible, but you will need to open and run each EG Project manually to test it § Don’t under estimate how long each project takes to migrate and test
- 25. Shane Gibson - http://blog.saasInct.com