Watch this Ask the Expert session to learn how to plan your migration to SAS Viya using SAS 9 Content Assessment.
Watch the webinar
You will learn:
- What the SAS 9 Content Assessment is.
- Why the SAS 9 Content Assessment is important.
- How to run the SAS 9 Content Assessment.
- How to review the results.
- The next steps.
The questions from the Q&A segment held at the end of the webinar are listed below and the slides from the webinar are attached.
Q&A
Even for the SAS 9.4 system evaluation? Since we’re doing a M4 to M7 migration, this sounds like it might be important.
SAS 9 System Evaluation can absolutely help with your migration to SAS 9.4 M7!
How do I access the free service?
SAS 9 Content Assessment can be downloaded from Downloads and Hotfixes on support.sas.com, https://support.sas.com/downloads/package.htm?pid=2465#
Our SAS 9.4 Foundation are asking about what their options are when trying to migrate to Viya? Does having the SAS Content Assessment require a Metadata Server?
Inventory, Profile and Gather SAS Code requires access to SAS Metadata Server. However, Code check and Summarize SAS Log Steps do not require the Metadata Server.
Is a specific platform needed to access and work with the report from the Data Mart?
SAS Viya 3.5 or higher is required. If you do not have SAS Viya yet, we offer a free service where you can share your data marts with SAS and only you and the SAS team you work with can log in and review the reports.
Is it possible to modify functions in the SAS code? For example, LENGTH into KLENGT?
Great suggestion. Not today, but I will make a request to R&D to create that app.
Is Proc Surveymeans or an alternative available for running in CAS?
When migrating SAS 9 code like PROC SURVEYMEANS to SAS Viya we only consider refactoring the SAS 9 code to run in CAS if the real time for that step is 30 minutes or longer.” For SAS 9 code that runs under 30 minutes we advise to run that code in the compute server of SAS Viya (SPRE).
How long does it take to run SAS 9 content assessment?
Well, it's all data driven. If you have very little metadata, I've seen inventory complete under 15 minutes. I've seen inventory take five hours. Profile is the longest running app and, again, that's dependent on your metadata. How many stored processes do you have? How many information maps? How many OLAP cubes, how many DI Studio jobs? There is no easy button to answer that – it takes as long as it takes. But, again, going back to that 88 hour just for DI Studio Jobs, it finished successfully. It just took 88 hours. Now, that's an outlier in my opinion. A lot of customers I work with, like the customer with the 3.5 million SAS programs, code check took 20 hours and publishing code check took another 20 hours.
Recommended Resources
How to use the SAS® 9 Content Assessment Tool
SAS 9 Content Assessment Download
3 Approaches to SAS Cloud Migration Webinar
Please see additional resources in the attached slide deck.
Want more tips? Be sure to subscribe to the Ask the Expert board to receive follow up Q&A, slides and recordings from other SAS Ask the Expert webinars.
Click image to register for webinar